The question wasn't why it fails, but why sometimes it goes through, why sometimes fail, and why is it retriggered<br>without any changes to the config or files (run 5 times the core-image-sato-sdk build in a row, and at least once it will fail).<br>
<br>I don't trust systems that are not deterministic :).<br><br>This being said:<br><br>grep -C5 -e 'CROSS COMPILE Badness:' -e 'is unsafe for cross-compilation' /home/ddalex/ssd/yocto/build/tmp/work/i586-poky-linux/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/build.i586-poky-linux.i586-poky-linux/gcc/config.log<br>
| return ldopen ();<br>| ;<br>| return 0;<br>| }<br>configure:8836: i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/ddalex/ssd/yocto/build/tmp/sysroots/qemux86 -o conftest -pipe -g -feliminate-unused-debug-types -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed conftest.c -L/usr/lib/cmplrs/cc2.11 -lmld >&5<br>
/home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld: warning: library search path "/usr/lib/cmplrs/cc2.11" is unsafe for cross-compilation<br>/home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld: cannot find -lmld<br>
collect2: error: ld returned 1 exit status<br>configure:8836: $? = 1<br>configure: failed program was:<br>| /* confdefs.h */<br>--<br>| return ldopen ();<br>| ;<br>| return 0;<br>| }<br>configure:8836: i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/ddalex/ssd/yocto/build/tmp/sysroots/qemux86 -o conftest -pipe -g -feliminate-unused-debug-types -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed conftest.c -L/usr/lib/cmplrs/cc3.11 -lmld >&5<br>
/home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld: warning: library search path "/usr/lib/cmplrs/cc3.11" is unsafe for cross-compilation<br>/home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld: cannot find -lmld<br>
collect2: error: ld returned 1 exit status<br>configure:8836: $? = 1<br>configure: failed program was:<br>| /* confdefs.h */<br><br><br><div class="gmail_quote">On Wed, Jul 4, 2012 at 5:45 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, 2012-07-04 at 17:32 +0300, Mihai Lindner wrote:<br>
> On 7/4/2012 3:55 PM, Damian, Alexandru wrote:<br>
> > Hi guys,<br>
> ><br>
> > From time to time I get errors building gcc (although I didn't trigger a rebuild!) when runnign<br>
> > bitbake core-image-sato-sdk<br>
> ><br>
> > The error is attached:<br>
> > /home/ddalex/ssd/yocto/build/tmp/work/i586-poky-linux/gcc-4.7.1+svnr188658-r2/temp/log.do_configure.20668<br>
> ><br>
> > What is causing this, is this a know bug ?<br>
> ><br>
> > Cheers,<br>
> > Alex<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Openembedded-core mailing list<br>
> > <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
> > <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><br>
> ><br>
><br>
> To get a hint on why it fails, check<br>
> in /home/ddalex/ssd/yocto/build/tmp/work/i586-poky-linux/gcc-4.7.1<br>
> +svnr188658-r2/gcc-4_7-branch/build.i586-poky-linux.i586-poky-linux/gcc/config.log if there's "CROSS COMPILE Badness:" or "is unsafe for cross-compilation".<br>
><br>
> #$ grep -e 'CROSS COMPILE Badness:' -e 'is unsafe for<br>
> cross-compilation' /home/ddalex/ssd/yocto/build/tmp/work/i586-poky-linux/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/build.i586-poky-linux.i586-poky-linux/gcc/config.log<br>
><br>
> `bitbake` will fail if `grep` has results.<br>
<br>
</div>It might be slightly more complex than this. gcc is ugly in that the<br>
compile task executes a ton of separate configure processes and it could<br>
be tripping up on the above expression on any one of those config.log<br>
files.<br>
<br>
Once you find the config.log, report back on which one it is and what<br>
the message says and then we can work through how to fix it.<br>
<br>
Cheers,<br>
<br>
Richard<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><br>
</div></div></blockquote></div><br>