Hmm, but what would the advantages of this be over the proposed solution
#10352: Properly link Haskell shared libs on ELF systems -------------------------------------+------------------------------------- Reporter: duncan | Owner: Type: task | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.11 (Linking) | Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: 5987 Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by trommler): Replying to [comment:10 Phyx-]: though? The parameter (or value in the environment variable) would not need to depend on the installation directory (of the RTS libs) but just say '''what''' flavour of RTS is wanted. The advantages are 1. User's don't need to learn the internal organisation of directories, which also might change with releases. 1. In scripts (testcases etc) we do not depend on those directory names either. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10352#comment:11 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler