Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1 Hardcoded LD_LIBRARY_PATH

closed
nobody
None
5
2002-07-30
2002-07-30
Anonymous
No

You make generour use of rpath. This is wrong!!!!
You should not assume that libraries are always located
in the same place for all machines, or that they do not
move. rpath is not a viable option in most cases it is
provided typicaly for more system level things that should
not change at all. Your use of rpath is bad. Linking of
shared libraries should occur with a simple
'-shared -Lpath -llibname' options on the command line.

Discussion

  • Allen Barnett
    Allen Barnett
    2002-07-30

    Logged In: YES
    user_id=9845

    This is the decision of libtool
    (http://www.gnu.org/software/libtool/) as invoked by
    autoconf (http://www.gnu.org/software/autoconf/). At
    ./configure time, libtool is supposed to figure out where
    everything is on YOUR system and construct the rpath options
    accordingly. There may be an autoconf command option which
    can control this; you can do './configure --help' to see
    what options libtool provides.

    Closing this bug report.

     
  • Allen Barnett
    Allen Barnett
    2002-07-30

    • status: open --> closed