Library Problem

Doug Hardie bc979 at lafn.org
Thu Nov 29 03:36:15 UTC 2012


I have installed 4 systems from the same FreeBSD 9.1-RC3 disk.  Three of them worked just fine.  The last one is causing a problem.  It will not look in /usr/local/lib/ for shared libraries.  I did the standard install, moved in some source, compiled it and tried to run it.  The library is there.  On the working systems ktrace shows:

  2259 intro    CALL  access(0x28066000,0<F_OK>)
  2259 intro    NAMI  "/lib/libsermons.so"
  2259 intro    RET   access -1 errno 2 No such file or directory
  2259 intro    CALL  access(0x28066000,0<F_OK>)
  2259 intro    NAMI  "/usr/lib/libsermons.so"
  2259 intro    RET   access -1 errno 2 No such file or directory
  2259 intro    CALL  access(0x28066000,0<F_OK>)
  2259 intro    NAMI  "/usr/lib/compat/libsermons.so"
  2259 intro    RET   access -1 errno 2 No such file or directory
  2259 intro    CALL  access(0x28066000,0<F_OK>)
  2259 intro    NAMI  "/usr/local/lib/libsermons.so"
  2259 intro    RET   access 0


On the failing system ktrace shows:

  6746 intro    NAMI  "/lib/libsermons.so"
  6746 intro    RET   access -1 errno 2 No such file or directory
  6746 intro    CALL  access(0x28066000,0<F_OK>)
  6746 intro    NAMI  "/usr/lib/libsermons.so"
  6746 intro    RET   access -1 errno 2 No such file or directory
  6746 intro    CALL  access(0x28066000,0<F_OK>)
  6746 intro    NAMI  "/usr/lib/compat/libsermons.so"
  6746 intro    RET   access -1 errno 2 No such file or directory
  6746 intro    CALL  access(0x28066000,0<F_OK>)
  6746 intro    NAMI  "/lib/libsermons.so"
  6746 intro    RET   access -1 errno 2 No such file or directory
  6746 intro    CALL  access(0x28066000,0<F_OK>)
  6746 intro    NAMI  "/usr/lib/libsermons.so"
  6746 intro    RET   access -1 errno 2 No such file or directory
  6746 intro    CALL  write(0x2,0x28060080,0x3c)
  6746 intro    GIO   fd 2 wrote 60 bytes
       "Shared object "libsermons.so" not found, required by "intro""


It never attempts to check /usr/local/lib.  I can't find any configuration item that affects that.  How can this be fixed?



More information about the freebsd-stable mailing list