-
Notifications
You must be signed in to change notification settings - Fork 846
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
Adding criterion to lts-9.5 causes failure to compile #3448
Comments
It builds fine for me. Weird thing is that since you're not on windows, the module linking is failing on should be completely empty. May be worth while to blow away |
You tried on windows? I'm not surprised you didn't see the same result. For
what it's worth, I did try multiple resolvers, some of which I had no local
snapshots version. I tried 9.2, 9.0, 8.5, 8.2, the version of code-log was
all different in the output but otherwise the build failure was the same.
I looked through the issues and saw other arch users have had linker issues
in the past, some recommended installing libncurses5 compat package. I have
this package installed already, I tried reinstalling it also to no avail.
|
No, I tried on linux. Perhaps arch's linker is atypically old or atypically new. I'm using ld version 2.26.1 . We should probably default to the gold linker - #3128 #2938 - but that hasn't been implemented yet. One possible hack might be to add a directory to the front of your PATH which has a symbolic link to the gold linker, renaming it to |
If anything it would be 'atypically new'. Arch is known for bleeding edge
packages. I can check what version when I'm home.
…On 22 September 2017 at 13:17, Michael Sloan ***@***.***> wrote:
No, I tried on linux. Perhaps arch's linker is atypically old or
atypically new. I'm using ld version 2.26.1 . We should probably default to
the gold linker - #3128
<#3128> #2938
<#2938> - but that
hasn't been implemented yet.
One possible hack might be to add a directory to the front of your PATH
which has a symbolic link to the gold linker, renaming it to ld... Not a
very nice hack, but could work
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3448 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABE3biIKsjbUVZvCCXW88XhKiNDLetanks5sk-uzgaJpZM4PgJwf>
.
--
Evan Cameron
|
My linker version is indeed much newer. |
I maybe meeting the same problem at now 😭 >>> uname -ar
Linux BlueAloha 4.6.0-1-surfacepro3 #1 SMP PREEMPT Wed Apr 5 14:12:33 JST 2017 x86_64 GNU/Linux >>> ld --version
GNU ld (GNU Binutils) 2.29
Copyright (C) 2017 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty. >>> stack --version | head -1
Version 1.5.1 x86_64 I updated haskell-stack at a few days ago, |
I fixed this problem on my environment ! $ yaourt -Rns libtinfo
$ yaourt -S ncurses5-compat-libs
$ rm -rf ~/.stack .stack-work
$ cd /usr/lib
$ sudo mv libncurses.so{,.bak}
$ sudo ln -s libncursesw.so.6.0 libncurses.so (the last half is this workaround) After this, |
I'll try it in a few hours, sure. |
I had the same issue with network, old-time, and clock, @aiya000's solution fixed it for me, thanks! |
@aiya000 why do you need to remove libtinfo? Any reason for that? also, it kinda sucks manually linking packages in /lib. I'm sure pacman or some other library is going to complain later. |
Seems like just removing I will close this issue. |
@leshow I found this way by lucky, but I cannot understand the reason 🤔 |
https://www.reddit.com/r/haskell/comments/7a1ty3/whats_the_correct_way_to_install_ghc_and_cabal_on/ I removed This works so long as you install any haskell packages through stack. |
General summary/comments (optional)
I created a new project with
stack new randomContent simple
it usedlts-9.5
I added thebytestrings
dependency to my cabal file, coded for a while, stack built fine. I wanted to benchmark my code so I addedcriterion
as a dependency also.Which causes this error:
Steps to reproduce
For example:
Include any
.yaml
configuration if relevant.stack.yaml is teh default provided by
stack new
Expected
I expected the dependency to be resolved without issue
Actual
adding criterion makes the build fail with a linker error,
Stack version
Method of installation
Installed from arch regular repos, not the AUR. System is up to date.
##Additional
I went back to try and rebuild packages with criterion in them that previously built just fine, I was unable to build them. They all fail on
code-page
with the-fPIC
errorThe text was updated successfully, but these errors were encountered: