path: root/meta/recipes-devtools/binutils/binutils-cross-canadian.inc
Commit message (Collapse)AuthorAgeFilesLines
* binutils: apply mingw fix only for binutils-cross-canadianSamuli Piippo2017-09-181-0/+2
| | | | | | | | | Whenever SDKMACHINE is set to mingw32, sdkmingw32 override is defined everywhere. This meant that value of LDGOLD was different also for binutils and binutils-cross depending whether SDKMACHINE was set or not. Signed-off-by: Samuli Piippo <samuli.piippo@qt.io> Signed-off-by: Ross Burton <ross.burton@intel.com>
* binutils: enable warn system direcotories in cross-canadian ldYuanjie Huang2016-10-281-0/+1
| | | | | | | | | Warn system directories requires a configuration option to be enabled. This patch enables the warning for cross-canadian ld, to align with the cross version. Signed-off-by: Yuanjie Huang <yuanjie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
* binutils-cross-canadian: Explicitly DEPEND on nativesdk-flex, we require it ↵Richard Purdie2014-07-251-1/+1
| | | | | | anyway Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: add/tweak SUMMARYPaul Eggleton2014-01-021-1/+1
| | | | Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
* cross-canadian: Handle powerpc linux verses linux-gnuspeRichard Purdie2013-10-301-0/+2
| | | | | | | | | | | | | | 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] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* 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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk: Switch to using nativesdk as a prefix, not a suffixRichard Purdie2012-08-311-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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Add with-sysroot to target binutilsKhem Raj2012-06-211-5/+2
| | | | | | | | | | | Also rearrange the recipes to have common bits in inc files and not include the target bb file everywhere. This lets us add specific options to specific recipes particularly target recipe in this case Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils-cross-canadian: Clear BBCLASSEXTEND as a native version of this ↵Richard Purdie2012-01-111-0/+2
| | | | | | recipe makes no sense Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils-cross-canadian: Allow ld-is-goldDerek Buitenhuis2012-01-051-1/+2
| | | | | | | | | In order to actually generate a toolchain (with bitbake meta-toolchain) that supports gold, binutils- cross-canadian also needs to be built this way. Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils-cross-canadian: Point sysroot to correct locationKhem Raj2011-10-241-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* binutils-cross-canadian.inc: disable -werror like -cross doesKoen Kooi2011-02-091-1/+2
| | | | | | | | | | | | | | The error this works around is: cc1: warnings being treated as errors gas/config/tc-arm.c: In function 'parse_operands': gas/config/tc-arm.c:1876:27: error: 'firsttype$defined' may be used uninitialized in this function gas/config/tc-arm.c:1876:27: error: 'firsttype$index' may be used uninitialized in this function Ideally it should get fixed properly, but let's mimic binutils-cross for now Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils*.inc: Recipe format cleanupScott Garman2010-12-231-3/+2
| | | | | | Cleanup some simple whitespace / line break issues. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
* 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/+6
| | | | | | | | | | | | | | 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/+16
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>