#1798: add better framework support to ghc
-----------------------------+----------------------------------------------
Reporter: guest | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: 6.10 branch
Component: Compiler | Version: 6.6.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: Multiple
Os: MacOS X |
-----------------------------+----------------------------------------------
Comment (by thorkilnaur):
I can confirm that your Linker.lhs is closer to dyld with respect to the
handling of frameworks than the original Linker.lhs: With the original
Linker.lhs and a recent HEAD, if I remove
{{{/Library/Frameworks/GNUreadlin}}}e and instead install a suitable
{{{$HOME/Library/Frameworks/GNUreadline}}}, then ghci is able to run, but
reports
{{{
Loading package readline-1.0.1 ... can't load framework: GNUreadline (not
found)
}}}
when asked to run this program:
{{{
module Main where
import System.Console.Readline as Readline
main = Readline.initialize
}}}
With your changed Linker.lhs, the program runs without complaints. So
based on that, I would say that your change makes sense.
While performing these tests, I noticed that dyld apparently also looks
for frameworks in the current directory. Perhaps judah - with dyld.cpp
(see http://hackage.haskell.org/trac/ghc/wiki/OSXFrameworks) - can confirm
this? In any case, there still seems to be some differences between the
set of places that dyld and your Linker.lhs search for frameworks.
Best regards
Thorkil
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1798#comment:5>
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
