I guess the root of the problem is when the autotools start up - we're having autoconf 2.68,<br>which is not liked by gcc 4.7.1<br><br><a href="http://configure.ac:33">configure.ac:33</a>: error: Please use exactly Autoconf 2.64 instead of 2.68.<br>
config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...<br><a href="http://configure.ac:33">configure.ac:33</a>: the top level<br>autom4te: m4 failed with exit status: 1<br><br><br>I'm gonna downgrade to autoconf 2.64 and see what happens.<br>
<br>Alex <br><br><div class="gmail_quote">On Wed, Jul 4, 2012 at 6:21 PM, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</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, Jul 04, 2012 at 06:06:55PM +0300, Damian, Alexandru wrote:<br>
> I guess the problem is no lmld, (skips over), Mihai says that<br>
><br>
> - library search path "/usr/lib/cmplrs/cc2.11" is unsafe for<br>
> cross-compilation<br>
<br>
</div>It's one of issues I sometimes see during gcc upgrades.. and it was<br>
there with e.g. gcc-4.6.3 too<br>
<a href="http://build.shr-project.org/tests/jama/gcc-issue/gcc.issue" target="_blank">http://build.shr-project.org/tests/jama/gcc-issue/gcc.issue</a> (from Jan<br>
14)<br>
<div class="HOEnZb"><div class="h5"><br>
> is the cause.<br>
><br>
><br>
> I'm unable to trace back the cc2.11 file name (path).<br>
><br>
><br>
><br>
> Let's take it bit by bit, we have two issues here.<br>
> 1. - why the configure hangs from time to time (what is that c2.11 ??)<br>
><br>
> 2. - why sometimes it triggers massive rebuild even if nothing is changed.<br>
><br>
> Regarding point 2, does anybody else sees it ?<br>
><br>
> Alex<br>
><br>
> On Wed, Jul 4, 2012 at 6:02 PM, Richard Purdie <<br>
> <a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br>
><br>
> > On Wed, 2012-07-04 at 17:50 +0300, Damian, Alexandru wrote:<br>
> > > The question wasn't why it fails, but why sometimes it goes through,<br>
> > > why sometimes fail, and why is it retriggered<br>
> > > without any changes to the config or files (run 5 times the<br>
> > > 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>
> > The check runs at the end of the do_configure task.<br>
> ><br>
> > The config.log is generated by do_compile. If do_configure is re-run,<br>
> > you'll hit the failure.<br>
> ><br>
> > > This being said:<br>
> > ><br>
> > > grep -C5 -e 'CROSS COMPILE Badness:' -e 'is unsafe for<br>
> > > cross-compilation'<br>
> > /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<br>
> > > --sysroot=/home/ddalex/ssd/yocto/build/tmp/sysroots/qemux86 -o<br>
> > > conftest -pipe -g -feliminate-unused-debug-types -Wl,-O1<br>
> > > -Wl,--hash-style=gnu -Wl,--as-needed conftest.c<br>
> > > -L/usr/lib/cmplrs/cc2.11 -lmld >&5<br>
> > ><br>
> > /home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld:<br>
> > warning: library search path "/usr/lib/cmplrs/cc2.11" is unsafe for<br>
> > cross-compilation<br>
> > ><br>
> > /home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld:<br>
> > 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>
> > So we need it to stop looking for libmld whatever that is. Hopefully<br>
> > there is a --disable-xxxx option we can pass in?<br>
> ><br>
> > Cheers,<br>
> ><br>
> > Richard<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>
> _______________________________________________<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>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Martin 'JaMa' Jansa jabber: <a href="mailto:Martin.Jansa@gmail.com">Martin.Jansa@gmail.com</a><br>
</font></span><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></blockquote></div><br>