linux/poky.git/meta/recipes-devtools/gcc/gcc-cross-initial.inc, branch dylan

classes: Be consistent about sstate-inputdirs/outputdirs ending with '/'

2012-11-14T14:38:28+00:00

If sstate-inputdirs and sstate-outputdirs don't match with ending '/' characters, the manifest file can end up corrupted. This change ensures the metadata is consistent in ending do_populate_root tasks with this character to avoid manifest file corruption. (From OE-Core rev: 3910eaf88d14904eef85b9e391387547df7fc54e) Signed-off-by: Richard Purdie

gcc-cross-initial: Reinstate limits.h generation fix

2012-09-06T23:07:42+00:00

The removal of gcc-cross-intermediate inadvertently reintroduced a problem with the limits.h file being incorrectly/inconsistently generated. http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b0faebd1f07e1616004bd19664395932e7c2c48f reverted part of: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c8815d2f21849deb9359706f54dc71490773415e This reintroduces the protected sysroot ensuring the limits.h file is always correctly generated. To reproduce the bug, build gcc-cross, then rebuild gcc-cross-initial and it will reference the limits.h file from gcc-cross in the sysroot. (From OE-Core rev: 71854f5c8c6850ed37777cad21acc92fdbea32fc) Signed-off-by: Richard Purdie

gcc-cross: Make gcc-cross-initial as the only intermediate gcc stage

2012-08-21T11:15:31+00:00

Now glibc can be compiled with gcc-cross-initial therefore prepare the stage to drop gcc-cross-intermediate Also drop arm-nolibfloat.patch should not be needed anymore half of changes in this patch are meant for OABI which we dont use anymore (From OE-Core rev: 30617bde61a3b0a0944b49a0c9fb7159dacbb19f) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc-cross-initial: Ensure it uses an isolated sysroot

2012-08-06T11:35:05+00:00

If we don't do this, a stale limits.h may be detected in STAGING_DIR_TARGET which would result in a different limits.h getting generated by gcc-cross-initial that references it. The referenced limits.h will then not get found by eglibc-initial causing rather strange build failures. The simplest solution is to create a temporary sysroot containing only the things gcc-cross-initial should care about and this results in a correct limits.h file regardless of what else may have been built. (From OE-Core rev: 9c304eae0724474902fe2f3150adc6af115af9ba) Signed-off-by: Richard Purdie

gcc-cross-initial: Fix typo causing limits.h not to be present

2012-08-03T06:50:36+00:00

(From OE-Core rev: f26014b1b2e7ae0a23829487ca0c0bc05043b5d7) Signed-off-by: Richard Purdie

gcc-cross-initial: Stage self sufficient fixed limits.h

2012-07-26T13:40:48+00:00

currently gcc installs a limits.h which references to another limits.h which it expects from target sysroot and that header in target sysroot will come from eglibc. So we need to break this catch-22 and hence we install a self sufficient limits.h which is then happy when referenced and doesnt complain about missing limits.h from target sysroot. This is mostly used when eglibc-initial configure is run (From OE-Core rev: eeb445ecbc651ad614a4fc492039bdad0747d45d) Signed-off-by: Khem Raj Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

gcc-cross-initial.inc: Use BFD ld as default always

2012-07-17T09:54:07+00:00

When using gold as default linker in final toolchain gcc-cross-initial still needs to use BFD ld since it will link eglibc-initial (From OE-Core rev: f643f886b16f586426c744afde080a99d71a9d58) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie Signed-off-by: Richard Purdie

crosssdk/nativesdk: Ensure EXTRA_OECONF_FPU is unset

2012-07-17T09:53:57+00:00

If EXTRA_OECONF_FPU is left set, certain ARM variables related to hard-float can get pulled in and trigger rebuilds of the crosssdk code. The best solution is to simply force the variable to a known correct value for the SDK targets currently supported in the same way as TARGET_FPU. There is some slight rearrangement of the gcc code to ensure the variable is always used to call the fpu function. (From OE-Core rev: 410990445ada8cdcfaec4e6fa5791cee9a5b8983) Signed-off-by: Richard Purdie Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

gcc-configure: Render --with-local-prefix harmless

2012-04-30T10:37:23+00:00

this option by default points to /usr/local no matter what so we cant let it sit on sidelines otherwise it will access host machine's /usr/local which may not be desired. So disable this option. This also helps in making gcc's shared state more consistent (From OE-Core rev: eee3658366e1ae9d3e429b3d3c968938d8d0f00e) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc: Stash the gcc-cross builddir to reuse in libgcc and gcc-runtime

2012-04-30T10:37:23+00:00

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 Signed-off-by: Richard Purdie