On Sunday 10 October 2004 19:41, Joe Morris (NTM) wrote:
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.
Yes, Joe, i see your point, and I agree. I think it is not our SuSE AMD64 system where we try to compile the apps which is doing something wrong. The apps usually come already with the configure script, and I think the error is there, which means the autoconf & friends system is responsible. And here SuSE is very well able to work with the maintainers to get it to generate configure scripts and makefiles which do also work with 64bit Linux systems. But when you say that the apps have it "hard coded to only look in /usr/lib (or /opt/kde3/lib instead of lib64)", then where is that hardcoded??? I do some programming, even in C++, using kdevelop, and I never did hardcode anywhere where to look for the libs. As far as I know, the libs are needed when the apps get linked, after compiling. The command to do so is specified in the makefile, by configure. And configure is build by autoconf & Co. Now I'm just scratching the surface of kde programming, so I might have misunderstood, but If I did get it more or less correctly, it means that somewhere in the creation of configure and / or the makefile, the correct lib path is not used. Joe, you say you patch the source, I assume you mean the c++ source, may I ask you for an example where you did patch? Thanks, Matt
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871