-
Notifications
You must be signed in to change notification settings - Fork 842
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
On Arch linux 'stack install' succeeds while 'stack ghci' doesn't #1135
Comments
What happens if you use Also, AFAIK, there's no inherent reason Stack on Arch has to use the system GHC/package. It would only do so if you have already installed GHC/packages separately from Stack (just like on Ubuntu and others). The haskell-stack package at https://aur.archlinux.org/packages/haskell-stack/ does not depend on any system GHC (but will use it if it's there). |
Also, @drwebb, as our resident Arch user, do you have input about why the system-installed GHC/packages would be causing this kind of trouble with |
I can confirm this issue is solved in Thanks for the support. |
I've never come across a problem where using the ghc package in the Arch Emanuel Borsboom writes:
Tristan Webb PhD |
I am trying to use
stack ghci
with language-puppet.stack install
works fine butstack ghci
gives me a compilation error. For instance:This error makes no sense to me because
stack build
It is important to note that:
Ubuntu 14.04.02 LTS Trusty Tahr
andstack ghci
works fine there.stack ghci
.stack clean
, I have another error:Could not find module ‘Paths_language_puppet’
. When Istack build
again and thenstack ghci
, I will get back the same compilation error.~/.ghci
does not make a differenceOne notable difference between the Ubuntu and the Arch linux setup, is the fact that in Ubuntu everything is installed by
stack
whereas inArch linux
, ghc and many other haskell packages are installed by Arch linux (via pacman)How to reproduce (on Arch linux):
Using Version 0.1.5.0 X86_64 on Arch linux.
As already discussed in #847, the problem is related to Arch linux. It is suggested in #847 that permissions could be the root cause. I have tested the proposed fix (make file permissions on Arch the same as in Ubuntu) but it did not fix the problem.
The text was updated successfully, but these errors were encountered: