On Sat, 2006-09-30 at 11:38 -0500, Arnie Stender wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Guys, > I'm missing something. I have re-compiled popt-1.10.4 with configure > switches --prefix=/usr and --libdir=/usr/lib. This seems to have > installed libpopt files properly in /usr/lib. Now I am going back and > re-compiling other libs that are dependent on libopt to make sure they > are looking in /usr/lib instead of /usr/lib64. Right now I am working on > libgnomeui and the compile errors out with the following. I'm going to > continue with my comments here so they don't get mixed up with the > supporting outputs. I found out that the libtools I found in the build > directories were being built from running the ./configure command. I had > thought there were just supplied in the package. In the error message > from the compile it says "grep: /usr/lib64/libpopt.la: No such file or > directory". That seems to say it is still picking up an absolute path of > /usr/lib64 somewhere. I have tried to re-compile each of the packages > that are dependent on popt and each comes up with the same error. I > think I may be stuck in a catch 22 but I'm not sure what to do to get > out of it. I did a grep for the lib64 in the .la files and I'll include > the output below. Does anyone have any suggestions? > > Arnie
I think that recompiling only popt is sufficient. ldconfig is probably run when you run "make install", so popt should be visible afterwards. If it doesn't run ldconfig, you can run it yourself. If you built a 64-bit system and not biarch, you could try creating a link called /lib64, and point it at /lib. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
