Cabal issue installing vect
mgsloan opened this issue · 7 comments
In order to build lambdacube-samples, I needed to build the vect package. This is really an issue with that package, but unfortunately there is no issue tracker for it, as this is its homepage: http://code.haskell.org/~bkomuves/ I figure this is an ok place to put the issue, though, since there are only a couple other reverse dependencies beyond bullet / lambdacube-*: http://packdeps.haskellers.com/reverse/vect
/usr/bin/ld.gold: error: cannot find -lHSrandom-1.0.1.1-ghc7.8.2
collect2: ld returned 1 exit status
Failed to install vect-0.4.7
cabal: Error: some packages failed to install:
vect-0.4.7 failed during the building phase. The exception was:
ExitFailure 1
Thankfully the fix for this was quite simple - cabal install random-1.0.1.1 --reinstall --enable-shared - but ideally such cabal-fu should be avoided - as such things can be a big barrier to entry. Why does vect need the dynamically linked version of random?
So anyway, ideally, either vect would be fixed or the dependency dropped.
vect seems like it's not actively being worked on anymore. Is there any interest in switching over to ekmett/linear ?
Switching is not entirely out of the question, but since we know the author of vect in person, we can bring up the problem with him first.
Sounds good! More info: I'm running GHC 7.8.2. Above, I was running cabal install 1.16, which I realized could be an issue. I've tried again in a fresh hsenv and cabal install 1.20, and got the same issue again, but oddly enough, I also got /usr/bin/ld.gold: error: cannot find -lHStext-1.1.1.3-ghc7.8.2 when building parsec. Anyone know what's going on here? I didn't run into such issues before GHC-7.8.2.
Specifying --enable-shared for every cabal install I run in the hsenv fixes the issue.
We’ll have a closer look, but it’s more likely that the problem is on your end. I just tried and successfully installed all the LambdaCube packages both with GHC 7.6.2 and GHC 7.8.2 (starting from a clean slate with each).
Gotcha, thanks for looking into it! I wonder what's wrong on my end.. Whatever it is, I don't think I've got anything too strange going on, so others will likely run into it too. I'm also starting with an empty hsenv.
We can’t seem to reproduce this problem.
I'm not seeing it anymore either - sorry for the noise! I think it might have been resolved by GHC 7.8.3, or due to recently starting with a new linux install.