Matt T. wrote:
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.
One example was ktail. Pasted here is the diff/patch to get it to build on x86_64. --- usr/src/packages/BUILD/ktail-0.6.1/configure 2002-07-03 18:56:04.000000000 -0500 +++ home/joe/configure 2004-09-01 12:18:09.860103188 -0500 @@ -7451,8 +7451,8 @@ kde_libraries=${exec_prefix}/lib ac_kde_libraries=$exec_prefix/lib else - kde_libraries=${prefix}/lib - ac_kde_libraries=$prefix/lib + kde_libraries=${prefix}/lib64 + ac_kde_libraries=$prefix/lib64 fi else ac_kde_includes= @@ -7502,8 +7502,8 @@ So, check this please and use another prefix!" 1>&2; exit 1; } fi -kde_libdirs="/usr/lib/kde/lib /usr/local/kde/lib /usr/kde/lib /usr/lib/kde /usr/lib/kde3 /usr/lib /usr/X11R6/lib /usr/local/lib /opt/kde3/lib /opt/kde/lib /usr/X11R6/kde/lib" -test -n "$KDEDIR" && kde_libdirs="$KDEDIR/lib $KDEDIR $kde_libdirs" +kde_libdirs="/usr/lib/kde/lib /usr/local/kde/lib /usr/kde/lib /usr/lib/kde /usr/lib/kde3 /usr/lib /usr/X11R6/lib /usr/local/lib /opt/kde3/lib64 /opt/kde/lib /usr/X11R6/kde/lib" +test -n "$KDEDIR" && kde_libdirs="$KDEDIR/lib64 $KDEDIR $kde_libdirs" kde_libdirs="$ac_kde_libraries $kde_libdirs" kde_libdir=NO Sorry but this wraps.
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.
I know some programs already have a configure script. Most recent kde apps can use the handy libsuffix argument.
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.
Sometimes I have seen the configure scripts is built, and have seen some of those (IIRC in the autoconf directory) that needed patching because of a hard coded /usr/lib that got passed on to configure or the Makefile. An example was dansguardian. I am not a programmer though, but I know what I needed in certain instances with certain programs to get them to build (rpms). So far, I think I have had good success after making patches to the programs after tracking down any errors, but i always only make changes to the programs (I don't honestly know enough to change the tools used to build). Since I have had a good success rate this way, I would assume that it may not be the tools, but as Andreas said, the programs
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?
See above. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871