[OE-core] gcc version mismatch in sdk generation

James Limbouris james at digitalmatter.com.au
Tue Aug 9 01:33:38 UTC 2011


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





More information about the Openembedded-core mailing list