[RH#91014] libtool-libs lt_dlopenext should try to load module.so from the explicit search path before trying the system search path

[Daniel Reed]

[From https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91014]



With testlib.so in the current working directory, but no testlib.la, 
lt_dlopenext("testlib") after lt_dlsetsearchpath(PWD) seems to check paths 
out of order:

Loading libtest.
open("/home/boston/dreed/BZ/ltdl/libtest.la", O_RDONLY) = -1 ENOENT (No such 
file or directory)
open("/lib/libtest.la", O_RDONLY)       = -1 ENOENT (No such file or directory)
open("/usr/lib/libtest.la", O_RDONLY)   = -1 ENOENT (No such file or directory)
 ...
open("libtest.la", O_RDONLY)            = -1 ENOENT (No such file or directory)
open("/home/boston/dreed/BZ/ltdl/libtest.so", O_RDONLY) = 3
Loaded library libtest successfully.

This is with libltdl from branch-1-5 from earlier today.


To confirm, create a simple testlib.so, then create an executable "loader"
that sets lt_dlsetsearchpath() to the current working directory, then calls 
lt_dlopenext("testlib"). Run the executable as:
  strace -e trace=open -F ./loader

libtool.info does not indicate an order for path versus extension traversal 
for lt_dlopenext. It does indicate that user-defined search paths take 
highest priority for lt_dlopen.

--
Daniel Reed <address@hidden>      http://people.redhat.com/djr/   Desktop and 
Cygwin