summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/binutils
AgeCommit message (Collapse)AuthorFiles
2011-01-21binutils: fix library RPATHsScott Garman2
This integrates the RPATH fixes we recently applied to libtool. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21binutils: Fix QA staging errors for target binutilsScott Garman1
* The spurious paths were caused by a -L on commandline which pointed to build dir. So we dont use -L <wordir> -liberty instead use the libiberty.a directly on commandline effects are same but .la does not have the workdir path in deplibs Patch obtained from OpenEmbedded, written by Khem Raj. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21binutils: forward-port the binutils-poison.patchScott Garman2
Update the binutils-poison.patch to apply cleanly on binutils 2.21 Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21binutils: upgrade to 2.21 and add libtool sysroot supportScott Garman18
* Upgraded binutils to v2.21 * Incorporated libtool sysroot patches from OE * Removed patches no longer needed or obsoleted by OE patches Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-06binutils: use default ${CC} instead of defining it ownKevin Tian2
binutils.inc exports its own ${CC} which is similar to default ${CC} but missing ${TOOLCHAIN_OPTION}, which makes --sysroot option lost when compiling target binutils which then further breaks sstate. Signed-off-by: Kevin Tian <kevin.tian@intel.com>
2010-12-23binutils*.inc: Recipe format cleanupScott Garman3
Cleanup some simple whitespace / line break issues. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2010-12-23binutils: delete unused patchesScott Garman5
These patches are not used by any current binutils recipe. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2010-12-16recipes-devtools: Add Summary informationMark Hatle1
Add Summary information and update Descripts as necessary. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2010-12-10Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH.Lianhao Lu1
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>
2010-12-10cross-canadian: pkg name includes target archLianhao Lu2
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>
2010-12-09SRC_URI Checksums AdditionalsSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2010-10-01binutils: Update the poison patchMark Hatle2
[BUGID #374] Previously the poison directories patch was present, but not enabled due to the lack of the configure option being set, and also the fact configure itself was not being patched. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2010-09-08binutils: add binutils_poison.patchNitin A Kamble5
and also correct the license field in the recipe This fixes [BUGID #245] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2010-08-27Major layout change to the packages directoryRichard Purdie25
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>