Problems with libtool an amd64
-----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? - -- Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD4DBQFAqz+dMDqogpR5tkMRAjzZAJwOuOpynljHlciOtltCWM74iP1eJgCXfSNl 7uc+mlBjpK8nsmXw0JiXgg== =WQPs -----END PGP SIGNATURE-----
On Wed, May 19, 2004 at 07:06:00AM -0400, 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?
Partially.
2) Should I report it?
3) Does anyone have a patch?
4) I can't possibly be the first one to notice this, right?
You have two .la files, which libtool does not yet grok. Run configure with LDFLAGS="-L/usr/lib64" ./configure ... , this will probably help. Ciao, Marcus
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.
Hi, On Wed, 19 May 2004, Sid Boyce wrote:
complained about not finding the library in /usr/lib. I asked the SuSE guy to have a go at building kmymoney ....................SILENCIO!
Ehm, if you think I'm here to build random packages for others, you misunderstood. I told you what could make libtool look into /usr/lib for libpcreposix.la, which is in exactly three cases: 1) another .la file explicitely has /usr/lib/libpcreposix.la listed, or includes silly things like -L/usr/lib in its dependency_list, 2) libtool itself contains /usr/lib in it's different *search_path_spec, or 3) libtool is called with -L/usr/lib arguments during linking. 2) and 3) are avoided by --enable-libsuffix=64 during configure, at least in recent enough KDE packages. Perhaps your kmymoney was too old, you can check if configure even supports that option. 1) would be a bug in other packages. With this information I expect that you go on and try to find out what broke, if you are still interested. For instance you can use /bin/sh -x to trace libtool runs, or post at least the relevant libtool commands which then breaks. You can also do printf style debugging of libtool itself to see from which file /usr/lib/libpcreposix.al comes.
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.
The system libtool has not all features required by C++ programs, and it links much slower. Ciao, Michael.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 May 2004 9:55 am, Michael Matz wrote:
Hi,
On Wed, 19 May 2004, Sid Boyce wrote:
complained about not finding the library in /usr/lib. I asked the SuSE guy to have a go at building kmymoney ....................SILENCIO!
Ehm, if you think I'm here to build random packages for others, you misunderstood. I told you what could make libtool look into /usr/lib for libpcreposix.la, which is in exactly three cases: 1) another .la file explicitely has /usr/lib/libpcreposix.la listed, or includes silly things like -L/usr/lib in its dependency_list, 2) libtool itself contains /usr/lib in it's different *search_path_spec, or 3) libtool is called with -L/usr/lib arguments during linking.
2) and 3) are avoided by --enable-libsuffix=64 during configure, at least in recent enough KDE packages. Perhaps your kmymoney was too old, you can check if configure even supports that option.
1) would be a bug in other packages.
With this information I expect that you go on and try to find out what broke, if you are still interested. For instance you can use /bin/sh -x to trace libtool runs, or post at least the relevant libtool commands which then breaks. You can also do printf style debugging of libtool itself to see from which file /usr/lib/libpcreposix.al comes.
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.
The system libtool has not all features required by C++ programs, and it links much slower.
Adding export LDFLAGS='-L /usr/lib64' before configure step in spec file worked. Adding --enable-libsuffix=64 did NOT work. Shouldn't this be reported to libtool maintainers? - -- Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAq259MDqogpR5tkMRAhQHAKCBGyzCYyoXdETx01L5y8DjvCQ/QACfXDxI R8BdQbprXjk9OE06fjZiJS8= =q641 -----END PGP SIGNATURE-----
Michael Matz wrote:
Hi,
On Wed, 19 May 2004, Sid Boyce wrote:
complained about not finding the library in /usr/lib. I asked the SuSE guy to have a go at building kmymoney ....................SILENCIO!
Ehm, if you think I'm here to build random packages for others, you misunderstood. I told you what could make libtool look into /usr/lib for libpcreposix.la, which is in exactly three cases: 1) another .la file explicitely has /usr/lib/libpcreposix.la listed, or includes silly things like -L/usr/lib in its dependency_list, 2) libtool itself contains /usr/lib in it's different *search_path_spec, or 3) libtool is called with -L/usr/lib arguments during linking.
NO!, I don't have any need for kmymoney, it was just a random app on freshmeat.net that I tried to see if it experienced the same problem as was reported by the other guy who was trying to build something else. I suggested it, so you could see first hand what was happening.
2) and 3) are avoided by --enable-libsuffix=64 during configure, at least in recent enough KDE packages. Perhaps your kmymoney was too old, you can check if configure even supports that option.
1) would be a bug in other packages.
With this information I expect that you go on and try to find out what broke, if you are still interested. For instance you can use /bin/sh -x to trace libtool runs, or post at least the relevant libtool commands which then breaks. You can also do printf style debugging of libtool itself to see from which file /usr/lib/libpcreposix.al comes.
I heard you LOUD and CLEAR, I tried all that and more, including "linux32" which seems to do nothing. There is no libpcreposix of any flavour in /usr/lib, it's in /usr/lib64. From all the posts seen here, there seems to be a particular problem that affects building many applications. My endeavours have been solely to see if I could help resolve the problem. I am a longtime SuSE user and do whatever I can (as do the others on the lists) to encourage people to stay with this excellent distro. There will be glitches and things that don't work right, we try to resolve these issues and enjoy using SuSE.
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.
The system libtool has not all features required by C++ programs, and it links much slower.
Ciao, Michael.
Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
Hmm perhaps it's an X server problem... I'm not sure if it's not hardware... Try init 3 then init 5 (from a tty console i.e ctrl+alt+f1) if it's crashing. Instead of rebooting and then see if that's the problem. If it works after restarting just X (and whatever other services you have in runlevel 5, which shouldn't be alot) then you know what it is. Still crashing... then i'm stumped. Kind regards Joel On Thu, 2004-05-20 at 04:08, Sid Boyce wrote:
Michael Matz wrote:
Hi,
On Wed, 19 May 2004, Sid Boyce wrote:
complained about not finding the library in /usr/lib. I asked the SuSE guy to have a go at building kmymoney ....................SILENCIO!
Ehm, if you think I'm here to build random packages for others, you misunderstood. I told you what could make libtool look into /usr/lib for libpcreposix.la, which is in exactly three cases: 1) another .la file explicitely has /usr/lib/libpcreposix.la listed, or includes silly things like -L/usr/lib in its dependency_list, 2) libtool itself contains /usr/lib in it's different *search_path_spec, or 3) libtool is called with -L/usr/lib arguments during linking.
NO!, I don't have any need for kmymoney, it was just a random app on freshmeat.net that I tried to see if it experienced the same problem as was reported by the other guy who was trying to build something else. I suggested it, so you could see first hand what was happening.
2) and 3) are avoided by --enable-libsuffix=64 during configure, at least in recent enough KDE packages. Perhaps your kmymoney was too old, you can check if configure even supports that option.
1) would be a bug in other packages.
With this information I expect that you go on and try to find out what broke, if you are still interested. For instance you can use /bin/sh -x to trace libtool runs, or post at least the relevant libtool commands which then breaks. You can also do printf style debugging of libtool itself to see from which file /usr/lib/libpcreposix.al comes.
I heard you LOUD and CLEAR, I tried all that and more, including "linux32" which seems to do nothing. There is no libpcreposix of any flavour in /usr/lib, it's in /usr/lib64. From all the posts seen here, there seems to be a particular problem that affects building many applications. My endeavours have been solely to see if I could help resolve the problem. I am a longtime SuSE user and do whatever I can (as do the others on the lists) to encourage people to stay with this excellent distro. There will be glitches and things that don't work right, we try to resolve these issues and enjoy using SuSE.
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.
The system libtool has not all features required by C++ programs, and it links much slower.
Ciao, Michael.
Regards Sid.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
participants (5)
-
Joel Wiramu Pauling -
Marcus Meissner -
Michael Matz -
Neal D. Becker -
Sid Boyce