Need info

[darkone66669]

I am using fedora 10 64bit. I downloaded and compiled xine-lib. It compiled and installed just like it was suppose to. It put the libs into /usr/local/lib. I modified ld.so.conf to include usr/local/lib and the output showed that it found xine-lib. Then when I tried to configure xine-ui it couldn't find xine-lib. I found a workaround though I'm not sure how it actually worked and that is what I would like to know. I uninstalled xine-lib the did a rpmbuild on it and it put the xine lib in lib64. then I did a rpmbuild on xine-ui and everything worked just fine. I'm curious why rpmbuild worked and ./configure; make; make install didn't. I'm curious just in case I run across the same problem again somewhere else and I don't have the option to build an rpm from the tars.

[PabloTwo]

Hello, and welcome to the forum-

I'm not sure I can answer your question with any certainty or authority, so, I won't answer it directly. But a couple of suggestions on your proceedures here.

Because so many compiled sourcecode packages use PREFIX=/usr/local, and Fedoras default is PREFIX=/usr, it's always a very good idea to specify that in the ./configure command:

./configure --prefix=/usr

That helps avoid packages not being installed into directories that other packages don't expect to initially find them and having to fiddle with the relocations to make it work.

The second thing that may or may not help in this case is when any package installes linked shared object files (.so), in case the 'install' routine forgot to do so, is to run the ldconfig command manually after you've done the install step. The ldconfig command will check through all known/expected locations and 'link' any .so files that haven't yet been linked to the other files they need to be to work.

[darkone66669]

I did run the ldconfig manually and it does look in /usr/local. There are also other compiled shared libraries in the same path and they work fine. But Thanks anyway for the input.