[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
multilib issues when cross-linking
From: |
Christian Parpart |
Subject: |
multilib issues when cross-linking |
Date: |
Fri, 16 Feb 2007 14:41:54 +0100 |
User-agent: |
KMail/1.9.6 |
Hi,
I'm on amd64, and want to build my package for both, x86 and amd64. so while
the latter works just fine, the first does not.
On AMD64, NVIDIA provides a /usr/lib{32,64}/libGL.la, but other graphics
vendors obviousely don't.
Below is an extract from my output from running make to build the x86 ABI
of given library:
/bin/sh ../libtool --tag=CXX --mode=link \
g++ -ansi -pedantic -march=athlon64 -O3 -pipe -DNDEBUG=1 \
-m32 -L/usr/lib32 -o example example.o \
captury/libcaptury.la -lGL -lX11 -lXext
However, when libtool is looking for GL library it finds
/usr/lib32/libGL.so*
/usr/lib{64,}/libGL.{la,so*}
I explicitely added LDFLAGS="-L/usr/lib32" to make sure it first looks there,
but still, libtool wants the 64bit version, because we have a .la file for it,
which is really not the desired effect.
I'd like to consider this a libtool bug, however, I'd like how you think about
it, and, how you'd fix it (from the build script's view) otherwise.
(I just can't delete /usr/lib{64,}/libGL.la or fake /usr/lib32/libGL.la.
Is there a way to limit libtools searchpath to the really wanted paths or mask
out the really unwanted paths somehow?
Regards,
Christian Parpart.
pgpOkpTfqLa5D.pgp
Description: PGP signature
- multilib issues when cross-linking,
Christian Parpart <=