summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
Commit message (Collapse)AuthorAgeFilesLines
* gcc-cross: don't use oe.path.relativeRoss Burton2014-03-071-1/+1
| | | | | | | | | | | Instead of using oe.path.relative, use the Python Standard Library function os.path.relpath. (From OE-Core rev: 90c3a0401c566e26d89a5c0410b2a51fe27b95b2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Replace one-line DESCRIPTION with SUMMARYPaul Eggleton2014-01-021-1/+1
| | | | | | | | | | | | | | A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. (From OE-Core rev: b8feee3cf21f70ba4ec3b822d2f596d4fc02a292) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Fix fortran buildRichard Purdie2013-12-021-0/+1
| | | | | | | | | When fortran was enabled, builds were failing due to a extra files. For now we can remove these and avoid the build failure. (From OE-Core rev: 2e60ef7fe63974e443a9ddc25c5eb4249ec37963) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross-canadian: Handle powerpc linux verses linux-gnuspeRichard Purdie2013-10-301-1/+4
| | | | | | | | | | | | | | | | | PowerPC toolchains can use the OS "linux" or "linux-gnuspe". This patch links them together so the one cross-canadian toolchain can support both. GCC_FOR_TARGET is set for the GCC recipe as otherwise configure can pick up an incorrect value. [YOCTO #5354] (From OE-Core rev: a1d6331238982b0c5d39b0a18794f6654b00d46a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross-canadian: Fix TUNE_PKGARCH referencesRichard Purdie2013-10-041-0/+5
| | | | | | | | | | | | | | | | | | The cross-canadian compilers are now build once per architecture but were being installed into tune specific locations which is incorrect. This adjusts things so they are make TARGET_ARCH specific. We gain the tune specific parts from the target sysroot which remains tune specific, the compiler and tools are independent ot that. binutils/gcc require sysroot options but since we reset at runtime, these shouldn't have dependencies in the sstate checksums. They are therefore also excluded. With these patches, switching machines does not result in a rebuild of *-cross-canadian and the compiler is correctly located and referenced in the target images. (From OE-Core rev: f58acab6414fe96d9e07ebbe86b348d2ac2bed5f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Fold configure-sdk and package-sdk into the main .incRichard Purdie2013-08-231-2/+125
| | | | | | | | | This also has the advantage of removing the confusing sdk naming which has been purged everywhere else in favour of cross-canadian. (From OE-Core rev: cbb63ca9e7e6d397198808e862f812f1012c74a7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Merge 4.7 and 4.8 recipes into common includeRichard Purdie2013-08-231-0/+19
| | | | | | | | This removes duplication and follows the pattern of the other gcc recipes. (From OE-Core rev: 3296c896f5a5ef7dd50ab4e00ddbf1c2476462dc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: enable multilib supportConstantin Musca2013-02-111-0/+1
| | | | | | | (From OE-Core rev: ee7331e3e7d0b38f3e19ccf7e394537f5f653a22) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian.inc: Add dependency on cross-gccKhem Raj2012-12-191-1/+1
| | | | | | | | | | | | | | | | gcc-cross-canadian uses cross compiler during libgcc build when building from sstate the build failed when building gcc-cross-canadian since it did not populate gcc-cross therefore add an explicit dependency on virtual/${TARGET_PREFIX}gcc to make sure that gcc-cross is available before building gcc-cross-canadian (From OE-Core rev: d9b7478e41e3065d01aa45d8d70fae2fc5ff6066) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Fix gettext dependencyRichard Purdie2012-10-101-1/+1
| | | | | | | | | | | There was a problem in commit ad23395cd1f6c0cbfcc6980b6071d589f9f6cde0 since gettext-nativesdk was translated to gettext instead of nativesdk-gettext. This fixes to use the correct dependency. (From OE-Core rev: a6e325342cb489e05927d6cb2bb0a24fa6c20ef8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk: Switch to using nativesdk as a prefix, not a suffixRichard Purdie2012-09-021-1/+1
| | | | | | | | | | | | | | | As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. (From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH.Lianhao Lu2010-12-101-1/+1
| | | | | | | | | | | Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH for cross-canadian packages. This is due to the TARGET_ARCH of x86_64 would results incorrect packaging in cross-canadian packages. The pacakge name appendix of x86_64 target in cross-canadian packages is x86-64. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
* cross-canadian: pkg name includes target archLianhao Lu2010-12-101-0/+4
| | | | | | | | | | | | | | This commit fixes Bug #528. 1. Added the target arch name to the pkg name of gcc-cross-canadian, gdb-cross-candian and bintuils-cross-candian. 2. Move the cross-canadian pkgs out of task-sdk-host into a new task task-cross-canadian. 3. Added the RDEPENDS of task-cross-canadian into meta-toolchain. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
* Major layout change to the packages directoryRichard Purdie2010-08-271-0/+4
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-23 08:23:31 +0000