Mailinglist Archive: opensuse-amd64 (449 mails)

< Previous Next >
Re: [suse-amd64] 64-bit libs and 32-bit libs
  • From: "Joe Morris (NTM)" <Joe_Morris@xxxxxxx>
  • Date: Sun, 10 Oct 2004 12:42:57 +0000 (UTC)
  • Message-id: <41692E0E.7020803@xxxxxxx>
Matt T. wrote:

Having the same problem, I looked into the makefile for some apps, and there it does indeed try to link to the libs in /usr/lib instead of /usr/lib64

I did just hack the makefile, and it works then, but the --enable-libsuffix=64 and / or --with-extra-libs=/usr/lib64 might do the same trick.

Now I do not know enough of autoconf / configure & Co, but I would look for the problem there. The makefile is created by configure, and configure by autoconf, so somewhere there the system does not recognize that it should link to the libs in /usr/lib64 and writes the makefile using /usr/lib instead.

Therefore, Andreas, I'm not so sure if it can be blamed on the apps. It might be the autoconf / configure part of compiling the apps, and there I think you could so something, couldn't you?

I have had a fair bit of success building apps on my 9.1, but I have found that there have been instances that apps have had it hard coded to only look in /usr/lib (or /opt/kde3/lib instead of lib64). It is not always easy to find where they have done it, but after patching the source to look in the lib64 directory I have been able to get most apps to build x86_64. So far, though, most apps will build with either the --enable-libsuffix=64 or adding export LDFLAGS="-L/usr/lib64". Anyway, I believe Andreas is correct, the problem with non-building packages on x86_64 is with the apps, not a problem with the system.

--
Joe Morris
New Tribes Mission
Email Address: Joe_Morris@xxxxxxx
Registered Linux user 231871







< Previous Next >
Follow Ups