From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc errors while building core-image-sato-sdk
Date: Wed, 04 Jul 2012 16:02:17 +0100 [thread overview]
Message-ID: <1341414137.3906.33.camel@ted> (raw)
In-Reply-To: <CAJ2CSBuRsmRDCaj5oY8xToURc3GkCJzRj8y6auzTUxA32AZBMQ@mail.gmail.com>
On Wed, 2012-07-04 at 17:50 +0300, Damian, Alexandru wrote:
> 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 :).
The check runs at the end of the do_configure task.
The config.log is generated by do_compile. If do_configure is re-run,
you'll hit the failure.
> 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 */
So we need it to stop looking for libmld whatever that is. Hopefully
there is a --disable-xxxx option we can pass in?
Cheers,
Richard
next prev parent reply other threads:[~2012-07-04 15:13 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
2012-07-04 14:45 ` Richard Purdie
2012-07-04 14:50 ` Damian, Alexandru
2012-07-04 15:02 ` Richard Purdie [this message]
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=1341414137.3906.33.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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