From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc version mismatch in sdk generation
Date: Tue, 09 Aug 2011 00:25:55 +0100 [thread overview]
Message-ID: <1312845955.14274.284.camel@rex> (raw)
In-Reply-To: <840A81C1B782724A8EB52725BD519EFF183257@MBX20.4emm.local>
On Mon, 2011-08-08 at 05:02 +0000, James Limbouris wrote:
> Hi,
>
> In oe-core, with Angstrom 2010.x, generating an sdk with:
>
> bitbake meta-toolchain-qte
>
> is giving me a toolchain with gcc-4.6.1 binaries in the i686 sysroot, but
> gcc-4.5.4 runtime libraries in the arm (target) sysroot. The sdk can't
> link until a symlink is installed to trick it into using the 4.5.4 libraries.
>
> I've checked the preferred versions, but they seem to be set consistently
> in the disto's conf file, at least as far as I can see.
>
> 'bitbake -s | grep gcc' gives:
> gcc :4.5-r39.1+svnr176640
> gcc-cross :4.5-r39.2+svnr176640
> gcc-cross-canadian-arm :4.5-r39.0+svnr176640
> gcc-cross-initial :4.5-r39.0+svnr176640
> gcc-cross-intermediate :4.5-r39.0+svnr176640
> gcc-crosssdk :4.5-r39.0+svnr176640
> gcc-crosssdk-initial :4.5-r39.0+svnr176640
> gcc-crosssdk-intermediate :4.5-r39.0+svnr176640
> gcc-runtime :4.5-r39.1+svnr176640
> gcc-runtime-nativesdk :4.6.1+svnr175454-r5 :4.5-r39.1+svnr176640
> gccmakedep 1:1.0.2-r3
> libgcc :4.5-r39.1+svnr176640
> libgcc-nativesdk :4.6.1+svnr175454-r3 :4.5-r39.1+svnr176640
The nativesdk and crosssdk versions need to match at the very least.
Cheers,
Richard
next prev parent reply other threads:[~2011-08-08 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 5:02 gcc version mismatch in sdk generation James Limbouris
2011-08-08 23:25 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-09 1:33 James Limbouris
2011-08-09 1:39 ` Khem Raj
2011-08-09 1:52 ` James Limbouris
2011-08-09 2:33 ` Khem Raj
2011-08-09 3:18 ` James Limbouris
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=1312845955.14274.284.camel@rex \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.