Re: [Ltib] bluez utils 3.x more issues

[Stuart Hughes]

Hi Peter,

Some packages are broken with respect to cross compiling.  In some cases
you need to go in and patch configure or libtool.  Take a look at
dist/lfs-5.1/gtk2/gtk2.spec:
perl -pi -e 's,^sys_lib_search_path_spec=.*,sys_lib_search_path_spec=,' libtool

I'm not saying this is your problem, but it may be that you need to do
something evil like this too.

Regards, Stuart

On Tue, 2008-02-12 at 10:56 +0000, Peter Wurmsdobler wrote:
> Hello Stuart,
> 
> Thanks for the help.
> 
> A still unresolved question comes from this:
> 
> >> make[2]: Entering directory 
> >> `/home/paw2/c7833/trunk/build/ltib/rpm/BUILD/bluez-utils-3.26/tools'
> >> /bin/sh ../libtool --tag=CC   --mode=link gcc 
> >> -I/home/paw2/c7833/trunk/binary/rootfs/usr/include    -Wall -O2 
> >> -D_FORTIFY_SOURCE=2   -o hcitool hcitool.o -lbluetooth 
> >> ../common/libhelper.a
> >> gcc -I/home/paw2/c7833/trunk/binary/rootfs/usr/include -Wall -O2 
> >> -D_FORTIFY_SOURCE=2 -o hcitool hcitool.o  /usr/local/lib/libbluetooth.so 
> >> ../common/libhelper.a
> >> /usr/local/lib/libbluetooth.so: could not read symbols: File in wrong 
> >> format
> 
> I notice that libtool receives as arrgument a "-lbluetooth", but 
> launches gcc with the absolute path "/usr/local/lib/libbluetooth.so". I 
> conclude that libtool will search for the bluetooth library and find the 
> wrong one. Why could that be?
> 
> I have tried the same with bluez-utils 2.25 and it works. libtool leaves 
> the "-lbluetooth" as it is.
> 
> peter
>