#3072: considerations for management of shared libs
----------------------+-----------------------------------------------------
Reporter: duncan | Owner:
Type: proposal | Status: new
Priority: normal | Milestone:
Component: None | Version: 6.10.1
Severity: normal | Resolution:
Keywords: | Testcase:
Os: Linux | Architecture: Unknown/Multiple
----------------------+-----------------------------------------------------
Comment (by duncan):
Should have linked to the docs for `$ORIGIN`:
Solaris:
http://docs.sun.com/app/docs/doc/805-3050/6j2tng0mg?l=ko&a=view
Solaris and Linux:
http://www.scons.org/wiki/UsingOrigin
GNU man ld.so
{{{
$ORIGIN and rpath
ld.so understands the string $ORIGIN (or equivalently ${ORIGIN}) in an
rpath specification (DT_RPATH or DT_RUNPATH) to mean the directory con‐
taining the application executable. Thus, an application located in
somedir/app could be compiled with gcc -Wl,-rpath,'$ORIGIN/../lib' so
that it finds an associated shared library in somedir/lib no matter
where somedir is located in the directory hierarchy. This facilitates
the creation of "turn-key" applications that do not need to be
installed into special directories, but can instead be unpacked into
any directory and still find their own shared libraries.
}}}
This may also be useful for binary distributions of ghc that use shared
libs.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3072#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
