From: Khem Raj <raj.khem@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc version mismatch in sdk generation
Date: Mon, 08 Aug 2011 19:33:28 -0700 [thread overview]
Message-ID: <4E409C78.2060908@gmail.com> (raw)
In-Reply-To: <840A81C1B782724A8EB52725BD519EFF1832E3@MBX20.4emm.local>
[-- Attachment #1: Type: text/plain, Size: 2215 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/08/2011 06:52 PM, James Limbouris wrote:
> On Tuesday, 9 August 2011 9:40 AM, Khem Raj wrote:
>> On Mon, Aug 8, 2011 at 6:33 PM, James Limbouris
>> <james@digitalmatter.com.au> wrote:
>>> On Tue Aug 9 01:25:55 CEST 2011, Richard Purdie wrote:
>>>> 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
>>>
>>> Yes - that's what is so confusing. They seem to match in the
>>> Angstrom conf:
>>
>>
>> what does SDKGCCVERSION contain ?
>>
>
> Hi,
>
> Here are edited highlights from bitbake -e | grep -i GCC:
>
Can you try attached patch ? this is for meta-angstrom
Thx
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk5AnHcACgkQuwUzVZGdMxSX3gCgiMm/l2eOjT992lsqKaxnfuno
QVUAniNpa6BtGGrOjwjxfGFSdYCoHMWm
=EeKC
-----END PGP SIGNATURE-----
[-- Attachment #2: 0001-angstrom-2010.x.conf-Pin-PREFERRED_VERSION_gcc-cross.patch --]
[-- Type: text/x-diff, Size: 1229 bytes --]
From 8d6f9db776f30a2a88972fdb08856e0799839a25 Mon Sep 17 00:00:00 2001
From: Khem Raj <raj.khem@gmail.com>
Date: Mon, 8 Aug 2011 19:18:32 -0700
Subject: [PATCH] angstrom-2010.x.conf: Pin
PREFERRED_VERSION_gcc-cross-canadian-${TRANSLATED_TARGET_ARCH}
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
conf/distro/angstrom-2010.x.conf | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/conf/distro/angstrom-2010.x.conf b/conf/distro/angstrom-2010.x.conf
index e47561a..6622a1f 100644
--- a/conf/distro/angstrom-2010.x.conf
+++ b/conf/distro/angstrom-2010.x.conf
@@ -106,6 +106,7 @@ PREFERRED_VERSION_binutils ?= "${ANGSTROM_BINUTILS_VERSION
PREFERRED_VERSION_binutils-cross ?= "${ANGSTROM_BINUTILS_VERSION}"
PREFERRED_VERSION_binutils-crosssdk ?= "${ANGSTROM_BINUTILS_VERSION}"
PREFERRED_VERSION_binutils-cross-canadian ?= "${ANGSTROM_BINUTILS_VERSION}"
+PREFERRED_VERSION_gcc-cross-canadian-${TRANSLATED_TARGET_ARCH} ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-cross ?= "${ANGSTROM_GCC_VERSION}"
--
1.7.5.4
next prev parent reply other threads:[~2011-08-09 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 1:33 gcc version mismatch in sdk generation James Limbouris
2011-08-09 1:39 ` Khem Raj
2011-08-09 1:52 ` James Limbouris
2011-08-09 2:33 ` Khem Raj [this message]
2011-08-09 3:18 ` James Limbouris
-- strict thread matches above, loose matches on Subject: below --
2011-08-08 5:02 James Limbouris
2011-08-08 23:25 ` Richard Purdie
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=4E409C78.2060908@gmail.com \
--to=raj.khem@gmail.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 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.