Linking error compiling Cabal with custom snapshot #1356
Closed
Comments
Thanks for the detailed report. I am able to reproduce this locally with stack-0.1.8.0 as well. |
@mgsloan: since you're working on changes to custom snapshots already, can you look into this? |
Sure! Should be possible to work on this in the next couple weeks. |
Downgrading to P2 since it doesn't seem to affect many people. Still something to keep in mind for the custom snapshots revamp. |
mgsloan
added a commit
that referenced
this issue
May 15, 2016
@hesselink I believe this is now fixed. The issue was that when building Cabal-1.22's Setup.hs, it was linking against Cabal-1.18. I've added a special case for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is similar to #1110 but that one is fixed for me, and this isn't. If I compile
Cabal-1.22.4.0
on a custom snapshot based onghc-7.8
which includes a newer unix than comes with that ghc (2.7.1.0 instead of 2.7.0.1), there is an error linking thesetup
executable for Cabal:The weird thing is that this only happens on linux (Ubuntu 14.04.1 LTS), not on Mac. I've uploaded a reproduction here. Further information: stack
Version 0.1.6.0, Git revision e22271f5ce9afa2cb5be3bad9cafa392c623f85c (2313 commits) x86_64
, ghc 7.8.3.The text was updated successfully, but these errors were encountered: