summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc/gcc-package-cross.inc
Commit message (Collapse)AuthorAgeFilesLines
* gcc-*-cross.inc: Fold common configuration into gcc-cross.incRichard Purdie2013-08-231-48/+0
| | | | | | (From OE-Core rev: 8f6df85ca90c038316ca1ed22e9c54f937f21406) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Split do_packagedata task from do_packageRichard Purdie2013-01-251-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Currently, do_rootfs has a dependency on all the do_package output being present due to its usage of the pkgdata directories. This means that if you run: bitbake xxxx-image -c rootfs you end up having to fetch and unpack all the do_package data which is usually large and inefficient. It also means rm_work has to leave all the do_package data lying around so rootfs works. This patch splits the actual creation of the pkgdata directory off into a separate task, "packagedata" which happens immediately after do_package. We can then remap the dependencies so this task is depended upon, not do_package. Sstate can then be programmed not to require do_package at the appropriate times. Whilst this patch doesn't do so, it opens the possibility of rm_work wiping out the do_package output from WORKDIR as long as it also removed the do_package stamp (both normal and setscene variants) and allowing more space savings with rm_work which has been regularly requested. (From OE-Core rev: 6107ee294afde395e39d084c33e8e94013c625a9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Stash the gcc-cross builddir to reuse in libgcc and gcc-runtimeKhem Raj2012-04-301-13/+1
| | | | | | | | | | | | | | | | | | | Currently we stash the libgcc install tree and then reuse that to populate libgcc recipe later. This mechanism does not work for gcc 4.7/trunk since now libstdc++ needs access to build tree of libgcc. This patch stashes the gcc-cross build tree and then reuses this in libgcc as well as in gcc-runtime recipe builds. Now we build libgcc in the libgcc recipe instead of just using the prebuilt install tree core-image-minimal build/run tested on all qemu machines (From OE-Core rev: 7cf9f0597648c0bdaa080976d74acfbfc4c8443d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "gcc-cross: aviod creating invalid symlinks"Richard Purdie2012-03-141-4/+2
| | | | | | | This reverts commit 7893e74311e53882d8f93ecb95a6bd9f5b14651e since it breaks the builds. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross: aviod creating invalid symlinksRobert Yang2012-03-141-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | There are several invalid symlinks in gcc-cross-initial, gcc-cross-intermediate and gcc-cross, these cause the error:(56 errors) tmp/work/i586-poky-linux/gcc-cross-initial-4.6.3+svnr184847-r23/temp/log.do_populate_sysroot: log.do_populate_sysroot:grep: /path/to/invalid/symlink: No such file or directory Avoid creating invalid symlinks would fix this problem. Use the: [ ! -e file ] || do_something But not use: [ -e file ] && do_something is because that if the "file" doesn't exist, then the whole statement would return false, and bitbake treats this an error, so use the "||" to let it always be true. [YOCTO #2095] (From OE-Core rev: 7893e74311e53882d8f93ecb95a6bd9f5b14651e) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Replace bb.data.expand(xxx, d) -> d.expand(xxx)Richard Purdie2012-03-051-1/+1
| | | | | | | | sed \ -e 's:bb.data.\(expand([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data.expand *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-package-cross.inc: Mark do_package* tasks as noexecRichard Purdie2012-01-231-0/+5
| | | | | | | | | These tasks don't do anything, this just avoids the overhead of forking to exec them. (From OE-Core rev: 6708b3e908ae383922703390ac2d39f40348e1b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-package-cross: Switch to using pattern matching to detect when to stash ↵Richard Purdie2011-07-051-12/+14
| | | | | | | | | | | | libgcc into the sysroot Currently, we stash libgcc if PN is gcc-cross or gcc-crosssdk. This patch changes it to work for *gcc-cross and *-gcc-crosssdk which means it will patch for multilib extended toolchains. (From OE-Core rev: a39cbed2ec887fb83335ba93e92d971c84a0f4d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix removal of libiberty.aRichard Purdie2011-07-051-2/+2
| | | | | | | | | | | | | The changes in commit 553a92c442bc3a35d1520a22e640a3a0e377b8f7 were not applying correctly due to the error: "find: paths must precede expression" This patch corrects the find syntax. [YOCTO #1199] (From OE-Core rev: b8d72e3af93ff9e2808fef4fe7b9d00b68bf9715) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-package-cross: also install the symlinks in libexec with target prefixPhil Blundell2011-06-061-0/+1
| | | | | | | | | | | .. since this is where collect2 seems to look for them. This seems like it is really a bug in collect2, but installing the symlinks is an easy workaround. Without this you get "could not find ld" errors when using -flto. (From OE-Core rev: d69561d80a995a52f3c7abfdbfd183fc7846046d) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: take out libiberty files from gcc packagesNitin A Kamble2011-03-031-0/+4
| | | | | | | | | this Fixes [BUGID #754] (From OE-Core rev: 553a92c442bc3a35d1520a22e640a3a0e377b8f7) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Major layout change to the packages directoryRichard Purdie2010-08-271-0/+47
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>