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@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@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
