-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linker issues around integer-gmp
on MacOS
#5222
Comments
/cc @bgamari does this ring any bells? |
I've seem something like with with in-tree-gmp. @harpocrates what's the exact error with your manually built 8.4 and the new-style haddock? Also, could you share both binaries somewhere?
This, I think, comes from ghcs internal linker. |
Woops! I goofed. I don't get an error with the new-style commands + manually built 8.4 - I get a compile error (sorry - I miscopied the summary from the Haddock thread):
(Worth noting I'm building the Haddock 2.19.0.1 release and GHC 8.4.1 release tags, so dependencies really should be working out) |
integer-gmp
and new-build
on MacOSinteger-gmp
on MacOS
@harpocrates that looks more like your |
@angerman I just did a fresh clone and (I've also been regularly nuking my |
Hmm... I’ll try to reproduce this later. |
Worth mentioning this isn't a blocker for me anymore - I'm just falling back onto my Ubuntu VM whenever I hit this. That said, I'm willing to put time into stepping through any sort of debugging ideas people may have. |
I'm still being hit by this, as it manifests itself on doctest: sol/doctest#199 Essentially, with GHC 8.4.1, doctest on Mac OSX simply doesn't run. Replicating from that ticket, it fails with:
Any help would be most appreciated! |
I see the same thing with hledger-lib doctests on mac with GHC 8.4.1, but FWIW I am using stack and the GHC it installed, not cabal old or new-build. |
anyone knows if GHC 8.4.2 will fix this problem? |
@bgamari ? |
I opened a GHC trac ticket for a very similar (maybe the same?) bug here and I think that is going to be fixed in 8.4.2. |
I'm afraid the problem is still there with ghc 8.4.2:
Can anyone else confirm? |
I can confirm. 😢 |
@harpocrates @bgamari Since the GHC bug you referenced is already closed as fixed, should we open a new one? I’m happy to do so, but you have more context. Let me know. |
I've reported this as a GHC API bug: https://ghc.haskell.org/trac/ghc/ticket/15105. |
If this is a GHC bug, can this ticket be closed? |
Closing in favour of https://ghc.haskell.org/trac/ghc/ticket/15105. |
I'm not really sure if this is a Cabal issue or a GHC one, but since old-build sometimes succeeds where new-build segfaults, I'm going to assume it might be Cabal. I ran across this when trying to get the Haddock test suite to run with GHC 8.4.1, you can see what I tried there: haskell/haddock#767.
I've only seen this happen on MacOS - everything worked just fine in my Ubuntu VM.
For each cell in this table I started by building Haddock (either the
ghc-8.4
or the official1.19.0.1
release branch - same result).new-style:
old-style:
Then, I created a test file with some TH in it:
Finally, I ran the compiled
haddock
withMain.hs
as an argument:new-style:
old-style:
While I was able to get this to work with a manually-built GHC-8.4 and with the old-style commands, everything else crashed when I called when I tried to run the
haddock
binary with an error of the form:The text was updated successfully, but these errors were encountered: