diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-04-15 18:05:53 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-04-15 18:09:52 +0100 |
| commit | e7135f14f3ef37f93f5c28b319464f3d6dd9b8da (patch) | |
| tree | 56ee61a5108e9dfac0ef6446efd5c51f078a7886 /meta/recipes-devtools/libtool/libtool-2.4.2.inc | |
| parent | daa4d625524dc330786858ade570918cff0bc5d3 (diff) | |
| download | openembedded-core-e7135f14f3ef37f93f5c28b319464f3d6dd9b8da.tar.gz openembedded-core-e7135f14f3ef37f93f5c28b319464f3d6dd9b8da.tar.bz2 openembedded-core-e7135f14f3ef37f93f5c28b319464f3d6dd9b8da.zip | |
gcc-configure-common.inc: Stop gcc looking at build system paths
There were puzzling failures when you make a force recompile of any gcc
component. The error was in do_configure with cross-compilation badness
being detected in config.log files.
gcc is different in that many of the config.log files are generated during
the do_compile phase. This means this host contamination issue has always
been present but only shows up on a rebuild.
The fix is to force the appropriate configuration variable to "none required"
then gcc won't look in the bad locations.
[YOCTO #2279]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/libtool/libtool-2.4.2.inc')
0 files changed, 0 insertions, 0 deletions