Neal D. Becker wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Is this a known problem?
I'm trying to build apt-0.5.15cnc6 from srpm on suse9.1 amd64.
make[1]: Entering directory `/home/nbecker/RPM/BUILD/apt-0.5.15cnc6/lua' libtool --mode=link gcc -O2 -g -o lua/lua lua/lua_lua-lua.o liblua.la -lz - -lbz2 gcc -O2 -g -o lua/lua lua/lua_lua-lua.o ./.libs/liblua.al -lm -ldl - -lz /usr/lib/libbz2.so ^[[0m/usr/lib/libbz2.so: could not read symbols: Invalid operation
As you see, libtool... -lbz2 decided to usr /usr/lib/libbz2.so instead of /usr/lib64.
There are both /usr/lib/libbz2.la and /usr/lib64/libbz2.la.
I have traced the problem as far as /usr/bin/libtool reading /usr/lib/libbz2.la instead of /usr/lib64 version.
Questions:
1) Is this a bug in libtool amd64?
2) Should I report it?
3) Does anyone have a patch?
4) I can't possibly be the first one to notice this, right?
- --
Someone raised this kind of problem last week and I thought I'd give it a try with kmymoney, just to see if I got a similar problem. A guy from SuSE replied a few times suggesting different things, but that didn't fix it. In the case of kmymoney, the configure script was generating libtool in the directory and it always came up with /usr/lib, even adding/changing libtool to lib64 didn't make a difference, it always complained about not finding the library in /usr/lib. I asked the SuSE guy to have a go at building kmymoney ....................SILENCIO! I haven't yet got back to finding out quite how libtool gets generated, it didn't use /usr/bin/libtool which appears to have all the lib paths set. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.