Hi,
I know this topic has been discussed on the mailing list before, but
I've not been able to pick out all of the relevant pieces of information
to solve the problem for my particular situation. Hopefully, someone on
the list can help.
My platform is ppc64 SLES 10 SP1, libtool version 1.5.24. I have a
project built using the standard tools -- aclocal, autoconf, automake.
The default configuration builds everything as 32-bit. Prior to
integrating libtool into this project, I was also able to build and
install 64-bit programs and libraries by prefacing my ./configure
command with:
CFLAGS="-m64" CXXFLAGS=-m64"
I've now integrated libtool into the project. The 32-bit build still
works fine, but when I try a 64-bit build (using the technique described
above), it fails with:
gcc -m64 -o urh_int urh_int.o /usr/lib/libbfd.so -liberty -ldl
/usr/lib/libbfd.so: could not read symbols: File in wrong format
The urh_int.o was compiled 64-bit, but /usr/lib/libbfd.so is a 32-bit
library. If I manually run the above command and replace
'/usr/lib/libbfd.so' with '-lbfd', the 64-bit urh_int program is built
successfully.
Can someone tell me the extra magic flags I need to set in order to get
libtool to do the right thing?
Thanks in advance.
-Maynard
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
