[GHC] #10352: Properly link Haskell shared libs on ELF systems

[GHC]

#10352: Properly link Haskell shared libs on ELF systems
-------------------------------------+-------------------------------------
        Reporter:  duncan            |                   Owner:
            Type:  task              |                  Status:  new
        Priority:  normal            |               Milestone:
       Component:  Package system    |                 Version:  7.11
      Resolution:                    |                Keywords:
Operating System:  Linux             |            Architecture:
 Type of failure:  None/Unknown      |  Unknown/Multiple
      Blocked By:                    |               Test Case:
 Related Tickets:                    |                Blocking:
                                     |  Differential Revisions:
-------------------------------------+-------------------------------------

Comment (by rwbarton):

 This might solve part of the problem with dynamic libraries on Android too
 (#10324).

 Is it necessary to put any rpath in the Haskell libraries? It might be
 better not to have one. If our assumption that the dynamic linker will
 prefer the rpath from the executable is correct, then it won't matter, but
 if it's wrong, then better to get a runtime error than silently use an RTS
 flavor other than the one the user specified.

 It does mean that a program that wants to `dlopen()` a Haskell library has
 to load the RTS first, or somehow set the runtime library path; but that's
 just one more hoop to jump through in addition to initializing the RTS,
 etc.

 If it really does matter for a specific Haskell library to have an rpath
 for the RTS then that can be added when linking the library, and again it
 seems better not to have "wrong" rpaths floating around in its
 dependencies.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10352#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler