#3550: Dynamic libraries don't work on Mac OS/X
-------------------------------+--------------------------------------------
 Reporter:  StephenBlackheath  |          Owner:  StephenBlackheath             
                 
     Type:  bug                |         Status:  new                           
                 
 Priority:  normal             |      Milestone:                                
                 
Component:  Compiler           |        Version:  6.11                          
                 
 Severity:  major              |     Resolution:                                
                 
 Keywords:  dynamic mac osx    |       Testcase:  
http://upcycle.it/~blackh/ghc/test-case.tar.bz2
       Os:  MacOS X            |   Architecture:  Unknown/Multiple              
                 
-------------------------------+--------------------------------------------
Comment (by StephenBlackheath):

 If there's general agreement with the approach, I'll write a patch for the
 docs.

 Another thing - this line in the patch...

 -install-name $(ghclibdir)/`basename "$$@" | sed
 's/^libHS//;s/[-]ghc.*//'`/`basename "$$@"`

 ...is a bit brittle because it second-guesses the behaviour of other
 makefiles, so some re-factoring is probably desirable here (assuming you
 decide to go with this approach).

 ---

 Some other Mac OS/X issues:

 1. The general wisdom of using absolute paths on Mac OS/X:  My take on it
 is that GHC does things the "Unix way" where it installs into an absolute
 location.  If you want to package your application up Mac OS/X style
 (where the whole directory is required to be moveable), then the developer
 needs to make a process for doing that anyway.  Perhaps at that point,
 they would just add the extra step of modifying all the shipped libraries
 to use relative paths (this can be done using a Mac OS/X system utility).

 2. You can't run an app (one that has a library and an executable in it)
 from the build tree because it wants to use the install location.  I don't
 know the solution to this, but it's only a minor annoyance mostly, and it
 seems to me that it could be dealt with later as a separate issue.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3550#comment:2>
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

Reply via email to