-
Notifications
You must be signed in to change notification settings - Fork 841
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 error makes it impossible to use a stack.(Mac Os High Sierra 10.13.6) #4328
Comments
Does the same thing happen with Stack v1.7.1? |
@borsboom Yes, it does. I did an update to version 1.9 hoping it will work but it doesn't. It was working before, only after I updated my macos Xcode toolchain that's when it broke. |
I am having the same issue with v1.7.1 with same symptoms. GCC version:
Stack setup log:
LTS 11.22 also doesn't work Hope it helps. |
Okay I have resolved my own issue. I have llvm installed in the env as well so there seems to be a mixup of versions (I have both apple clang-10 and LLVM 7 installed). The resolution is to remove llvm 7 from PATH |
@borsboom Should this require a documentation fix? |
@fangyi-zhou Solution works, I had LLVM on my path, removing it works. |
@dbaynard Might be worth adding to the FAQ. I think this is an uncommon scenario only for people who've installed a non-standard toolchain. |
I added some FAQ in #4366. |
Might people install LLVM for other purposes? I suppose if that's the case, somebody can reopen this issue. |
General summary/comments (optional)
A link error occurs on every stack command which renders stack most of the stack features unusable.
Steps to reproduce
stack setup
Expected
Successfully install ghc and initial setup
Actual
If you suspect that a stack command misbehaved, please include the output of that command in
--verbose
mode.If the output is larger than a page please paste the output in a Gist.
Stack version
Method of installation
Version 1.9.0.1, Git revision a2489de02cb1c7d28b74c69bc66d2402268ccb0a (6123 commits) x86_64 hpack-0.31.0
The text was updated successfully, but these errors were encountered: