* gcc version mismatch in sdk generation
@ 2011-08-08 5:02 James Limbouris
2011-08-08 23:25 ` Richard Purdie
0 siblings, 1 reply; 7+ messages in thread
From: James Limbouris @ 2011-08-08 5:02 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org
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
Regards
James Limbouris
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gcc version mismatch in sdk generation
2011-08-08 5:02 gcc version mismatch in sdk generation James Limbouris
@ 2011-08-08 23:25 ` Richard Purdie
0 siblings, 0 replies; 7+ messages in thread
From: Richard Purdie @ 2011-08-08 23:25 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gcc version mismatch in sdk generation
@ 2011-08-09 1:33 James Limbouris
2011-08-09 1:39 ` Khem Raj
0 siblings, 1 reply; 7+ messages in thread
From: James Limbouris @ 2011-08-09 1:33 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org
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:
#Everybody else can just use this:
ANGSTROM_GCC_VERSION ?= "4.5"
ANGSTROM_BINUTILS_VERSION ?= "2.20.1"
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 ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-cross ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-cross-initial ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-cross-intermediate ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-cross-canadian ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-crosssdk ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-crosssdk-initial ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-crosssdk-intermediate ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-runtime ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_gcc-runtime-nativesdk ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_libgcc ?= "${ANGSTROM_GCC_VERSION}"
PREFERRED_VERSION_libgcc-nativesdk ?= "${ANGSTROM_GCC_VERSION}"
Regards
James Limbouris
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: gcc version mismatch in sdk generation
2011-08-09 1:33 James Limbouris
@ 2011-08-09 1:39 ` Khem Raj
2011-08-09 1:52 ` James Limbouris
0 siblings, 1 reply; 7+ messages in thread
From: Khem Raj @ 2011-08-09 1:39 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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 ?
>
> #Everybody else can just use this:
> ANGSTROM_GCC_VERSION ?= "4.5"
>
> ANGSTROM_BINUTILS_VERSION ?= "2.20.1"
>
> 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 ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-cross ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-cross-initial ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-cross-intermediate ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-cross-canadian ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-crosssdk ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-crosssdk-initial ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-crosssdk-intermediate ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-runtime ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_gcc-runtime-nativesdk ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_libgcc ?= "${ANGSTROM_GCC_VERSION}"
> PREFERRED_VERSION_libgcc-nativesdk ?= "${ANGSTROM_GCC_VERSION}"
>
> Regards
> James Limbouris
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: gcc version mismatch in sdk generation
2011-08-09 1:39 ` Khem Raj
@ 2011-08-09 1:52 ` James Limbouris
2011-08-09 2:33 ` Khem Raj
0 siblings, 1 reply; 7+ messages in thread
From: James Limbouris @ 2011-08-09 1:52 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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:
# PREFERRED_VERSION_gcc-cross-intermediate=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-cross-intermediate="4.5"
# PREFERRED_VERSION_gcc-cross-initial=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-cross-initial="4.5"
# SDKGCCVERSION=4.6%
SDKGCCVERSION="4.6%"
# GCCVERSION=4.6%
GCCVERSION="4.6%"
# PREFERRED_VERSION_gcc-cross=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-cross="4.5"
# PREFERRED_VERSION_gcc-runtime-nativesdk=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-runtime-nativesdk="4.5"
# PREFERRED_VERSION_gcc-crosssdk=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-crosssdk="4.5"
# PREFERRED_VERSION_libgcc=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_libgcc="4.5"
# PREFERRED_VERSION_libgcc-nativesdk=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_libgcc-nativesdk="4.5"
# PREFERRED_VERSION_gcc-cross-canadian=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-cross-canadian="4.5"
# PREFERRED_VERSION_gcc-cross-canadian-${TRANSLATED_TARGET_ARCH}=${GCCVERSION}
PREFERRED_VERSION_gcc-cross-canadian-arm="4.6%"
# PREFERRED_VERSION_gcc-crosssdk-intermediate=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-crosssdk-intermediate="4.5"
# PREFERRED_VERSION_gcc=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc="4.5"
# PREFERRED_VERSION_gcc-crosssdk-initial=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-crosssdk-initial="4.5"
# ANGSTROM_GCC_VERSION=4.5
ANGSTROM_GCC_VERSION="4.5"
# PREFERRED_VERSION_gcc-runtime=${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc-runtime="4.5"
James
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: gcc version mismatch in sdk generation
2011-08-09 1:52 ` James Limbouris
@ 2011-08-09 2:33 ` Khem Raj
2011-08-09 3:18 ` James Limbouris
0 siblings, 1 reply; 7+ messages in thread
From: Khem Raj @ 2011-08-09 2:33 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
[-- 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
^ permalink raw reply related [flat|nested] 7+ messages in thread* Re: gcc version mismatch in sdk generation
2011-08-09 2:33 ` Khem Raj
@ 2011-08-09 3:18 ` James Limbouris
0 siblings, 0 replies; 7+ messages in thread
From: James Limbouris @ 2011-08-09 3:18 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-08-09 3:23 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-08 5:02 gcc version mismatch in sdk generation James Limbouris
2011-08-08 23:25 ` Richard Purdie
-- 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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox