From: Mihai Lindner <mihaix.lindner@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: gcc errors while building core-image-sato-sdk
Date: Wed, 04 Jul 2012 17:32:12 +0300 [thread overview]
Message-ID: <4FF453EC.8030007@linux.intel.com> (raw)
In-Reply-To: <CAJ2CSBsPhAtmpoTpBRzfqghV6tnRQXmjpcY415h=XfXtHxQzHQ@mail.gmail.com>
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.
--
Mihai Lindner
Yocto Project
next prev parent reply other threads:[~2012-07-04 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:55 gcc errors while building core-image-sato-sdk Damian, Alexandru
2012-07-04 14:32 ` Mihai Lindner [this message]
2012-07-04 14:45 ` Richard Purdie
2012-07-04 14:50 ` Damian, Alexandru
2012-07-04 15:02 ` Richard Purdie
2012-07-04 15:06 ` Damian, Alexandru
2012-07-04 15:21 ` Martin Jansa
2012-07-05 6:51 ` Damian, Alexandru
2012-07-05 20:03 ` Khem Raj
2012-07-06 8:55 ` Richard Purdie
2012-07-06 16:00 ` Khem Raj
2012-07-06 17:23 ` Saul Wold
2012-07-07 0:54 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FF453EC.8030007@linux.intel.com \
--to=mihaix.lindner@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox