#5289: Can't use ghci with a library linked against libstdc++
---------------------------------+------------------------------------------
Reporter: bos | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 7.2.1
Component: GHCi | Version: 7.0.3
Keywords: | Testcase:
Blockedby: | Difficulty:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: GHCi crash
---------------------------------+------------------------------------------
Comment(by bos):
Replying to [comment:24 simonmar]:
> bos: I'm looking at this and I'm not sure I agree with your original
suggestion, that we should record the full path name to the versioned
`.so` because the user may not have installed the appropriate `-devel`
package.
I was coming to this with the perspective that `ghci` is effectively doing
runtime linking. If you don't agree, that's fine :-)
The main consequence of the distinction that I can see is that a
{{{#!/usr/bin/runghc}}} script will not work under your view of things
unless a `-devel` package is installed. I've never seen such a script in
the wild except for `Setup.lhs`, so that doesn't seem like a big deal to
me.
> So unless anyone persuades me otherwise, I'm going to implement the
simple fix I described above, which is to use `gcc --print-file-name` as
another strategy for mapping library names to file names in GHCi.
Cool! Will that same fallback work for both `runghc` and Template Haskell?
Certainly TH is affected by this bug, so I assume that all users of the
GHC API would be. (Actually, that makes me wonder about some of the web-
development packages that use dynamic reloading.)
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5289#comment:25>
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
