Patchwork gcc version mismatch in sdk generation

login
register
mail settings
Submitter Khem Raj
Date Aug. 9, 2011, 2:33 a.m.
Message ID <4E409C78.2060908@gmail.com>
Download mbox | patch
Permalink /patch/9527/
State New, archived
Headers show

Comments

Khem Raj - Aug. 9, 2011, 2:33 a.m.
-----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-----
James Limbouris - Aug. 9, 2011, 3:18 a.m.
On Tuesday, 9 August 2011 10:33 AM, Khem Raj wrote:
> 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

Thanks Khem, that did the trick.

James

Patch

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