Re: Question: is 'gcc' supposed to replace the libstdc++.la installed by 'gcc-cross'?

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 17-05-10 07:55, Khem Raj wrote:
> On (17/05/10 07:44), Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> I just noticed that after doing 'bitbake gcc' the old libstdc++ gets
>> replaced and the new one has:
>>
>> dependency_libs='
>> /OE/angstrom-dev/sysroots/armv6-angstrom-linux-gnueabi/usr/lib/libstdc++.la'
>>
>> instead of the expected '-lm'. It now refers to itself :(
> 
> hmmm target gcc should not have staged libstdc++ if it was already staged
> by gcc-cross but the problem is casued by
> gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch it passed the native libdir which
> is build_libdir even for target library builds using -rpath. I am currently
> looking into the reason. If possible we can get rid of that patch.

I'm getting a build failure with 'gcc' now failing to find libstc++.la.
I'm trying a build from scratch now to rule out any packaged-staging
problems (>1 recipes installing the same file, pstage removing it prior
to build).

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFL8Q57MkyGM64RGpERAvvpAJ4vR4wtskIhV6BBUN/LcOzxXYPSEwCeNNtm
FWhLXTLoZUXa+yIDjlEiNbo=
=EvPm
-----END PGP SIGNATURE-----