Dynamic library loader search path

Loader searches for dynamic libraries in directories specified in
$LD_LIBRARY_PATH environment variables. However it's not all, loader
also searches in directories in $LD_LIBRARY_PATH augmented with many
sub-paths like lib/i686/mmx, tls, mmx, i686 and so on. Where do these
sub-paths come from ? Is it possible to configure them or even cancel
them ? The problem I encountered is that loader first searches within
directories suffixed with all these sub-passes and only then in the
directory itself. This highly increases dynamic library search time.

.

Relevant Pages

  • Re: loader of X Windows implementation - newbie
    ... So upon start of the X server, ... I wonder why why not use *.so dynamic libraries instead of static libs? ... and if *.so libraries were used - could we use the glibc loader? ... by "driver" do you mean a krenel module or something of the xfree server? ...
    (comp.os.linux.x)
  • Re: Affecting dynamic library load path programmatically on solaris
    ... two dynamic libraries using dlopen + dlsym. ... and the loader will load *exactly* the library you asked it to? ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.programmer)
  • Re: loader of X Windows implementation - newbie
    ... >I see that in loadmod.c there is a method LoadModule for loading a module. ... >is the full implementation of this loader which is not simple ... Dynamic libraries mainly export symbols; they do not import symbols from ... For ELF libraries it _is_ possible to import global symbols (and a whole ...
    (comp.os.linux.x)