ldso

[Erik Bågfors]

It looks like to don't know the difference between ldpreload and the
normal ld-stuff.

My guess.

What you want to do is run your self compiled applications that needs
some self compiled library.  If so, all you need to do is put the
path(s) to the directories where you have the libraries in
/etc/ld.so.conf. ld.so.conf provides the system with paths to
directories where it can look for libraries.

Preload on the other hand is to load a specific library before running
the app.  The use for this is most often that you want to replace a
specific function in a library with a function you've written
yourself. Then you put your replacement in a specific library that you
build yourself and then you preload it.

Now to the real 1000 dollar question, why did you build these
applications yourself instead of just installing them with apt?

Regards,
Erik

On 4/28/05, Craig Jackson <cjackson at localsurface.com> wrote:
> Hi,
> I have my first experience with Ubuntu and it's very very nice. I am
> using for a mail gateway on an amd64. Ubuntu provides me with the base
> server and I compile the primary daemon server software like exim (4.50)
> and mysql (4.1.11).
> 
> The problem is the system library cache. ldconfig works but in order to
> get the libraries at boot I believe I need to use ld.so.preload-manager.
> ldso used to work by adding directory path to the libraries to the ld.so
> file, but it appears that ld.so.preload-manager can only handle the path
> to individual files themselves. I added the directory and had to boot
> into Knoppix to delete the preload file. How does ld.so.preload-manager
> work [I have read to man page] but I need to know for sure because I
> don't want to have to use Knoppix again?
> 
> Thanks,
> Craig Jackson
> 
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>