Re: Request for branch merge

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

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

On 13-04-10 05:46, Richard Purdie wrote:
> On Tue, 2010-04-13 at 00:19 +0200, Koen Kooi wrote:
>> OK, I reproduced the abiword failure, it's in enchant:
>>
>> | /bin/sh ../../arm-angstrom-linux-gnueabi-libtool --tag=CC
>> - --mode=link ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a
>> - -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
>> -
>> -isystem/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include
>> - -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2
>> - -ggdb3 -module -avoid-version -no-undefined
>> - -L/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
>> -
>> -Wl,-rpath-link,/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
>> - -Wl,-O1 -Wl,--hash-style=gnu -o libenchant_aspell.la -rpath
>> /usr/lib/enchant aspell_provider.lo -Wl,--export-dynamic -pthread
>> - -lgmodule-2.0 -lrt -lglib-2.0
>> - -L/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
>> - -laspell ../../src/libenchant.la
>> | /bin/grep:
>> /OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la:
>> No such file or directory
>> | /bin/sed: can't read
>> /OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la:
>> No such file or directory
>> | arm-angstrom-linux-gnueabi-libtool: link:
>> `/OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la'
>> is not a valid libtool archive
>>
>> The file referenced
>> (/OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la)
>> doesn't exist since it is located in
>> /OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/libstdc++.la
>> instead.
>>
>> Any clues in which direction I should look to debug this?
> 
> Sorry I've not been able to spend the time I'd like on this stuff, work
> and travel have got in the way and are probably going to tie me up for a
> while yet if I'm realistic. Anyone at ELC should say hello btw! :) 


> Jet lag prevents me thinking too clearly at the moment but whats
> happening above is that the sysroot is starting to look more like the
> real target filesystem and libstdc++ is moving to what I would say is
> the correct place for it. This is good but it seems something, probably
> a .la file has the incorrect path? Is this a build from scratch or an
> old build? I suspect it would work with a build from scratch but if this
> was one, there is some more subtle problem :/.

It's a complete build from scratch (rm tmp -rf ; bitbake abiword).

regards,

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

iD8DBQFLxBfsMkyGM64RGpERAiykAJwNRGHh69Gq4cO+ey3U/+MiPqo+tQCfeKzS
G2KKVQZabSMFEkaoC/9CIXs=
=eBAr
-----END PGP SIGNATURE-----