[OE-core] gcc errors while building core-image-sato-sdk

[Damian, Alexandru]

The question wasn't why it fails, but why sometimes it goes through, why
sometimes fail, and why is it retriggered
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).

I don't trust systems that are not deterministic :).

This being said:

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
| return ldopen ();
|   ;
|   return 0;
| }
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
/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
/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
collect2: error: ld returned 1 exit status
configure:8836: $? = 1
configure: failed program was:
| /* confdefs.h */
--
| return ldopen ();
|   ;
|   return 0;
| }
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
/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
/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
collect2: error: ld returned 1 exit status
configure:8836: $? = 1
configure: failed program was:
| /* confdefs.h */


On Wed, Jul 4, 2012 at 5:45 PM, Richard Purdie <
richard.purdie at linuxfoundation.org> wrote:

> On Wed, 2012-07-04 at 17:32 +0300, Mihai Lindner wrote:
> > On 7/4/2012 3:55 PM, Damian, Alexandru wrote:
> > > Hi guys,
> > >
> > > From time to time I get errors building gcc (although I didn't trigger
> a rebuild!) when runnign
> > > bitbake core-image-sato-sdk
> > >
> > > The error is attached:
> > >
> /home/ddalex/ssd/yocto/build/tmp/work/i586-poky-linux/gcc-4.7.1+svnr188658-r2/temp/log.do_configure.20668
> > >
> > > What is causing this, is this a know bug ?
> > >
> > > Cheers,
> > > Alex
> > >
> > >
> > > _______________________________________________
> > > Openembedded-core mailing list
> > > Openembedded-core at lists.openembedded.org
> > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> > >
> >
> > To get a hint on why it fails, check
> > in /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
> if there's "CROSS COMPILE Badness:" or "is unsafe for cross-compilation".
> >
> > #$ grep -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
> >
> > `bitbake` will fail if `grep` has results.
>
> It might be slightly more complex than this. gcc is ugly in that the
> compile task executes a ton of separate configure processes and it could
> be tripping up on the above expression on any one of those config.log
> files.
>
> Once you find the config.log, report back on which one it is and what
> the message says and then we can work through how to fix it.
>
> Cheers,
>
> Richard
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120704/5f710879/attachment-0002.html>