-
Notifications
You must be signed in to change notification settings - Fork 697
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
Cabal doesn't see happy on PATH #9904
Comments
Cabal does make use of the path environment variable. "extra-prog-path" as it says is just an extra path to augment the existing system path. It is not clear to me how your system is configured that this does not work. Perhaps when you enter the nix-shell the path is overridden? |
If @yaitskov, we need your help to diagnose this, |
I started grepping cabal source code - exception is thrown from lookupProgram which looks into a some Db and I assumed that program is referred in such a way is expected to be "cabally installed". I didn't trace all way. Here is another way to reproduce the issue, which is easier to investigate
|
This is a bug in the 1.20.1 and 1.21.0 happy releases (which are long deprecated). haskell/happy#274 is an entry-point to that story, I suppose. Happy version 1.20.1.1 is currently the most recent version that should install as expected. Meanwhile we fixed the situation on happy |
Thanks Sebastian! I wonder if we should close it in the light of the above. |
Describe the bug
cabal fails to build happy complaining that happy executable is not found, nonetheless happy is on PATH
To Reproduce
System information
Workaround
I guess it is expected behavior, but the fact that cabal is using alternative PATH not related to canonical BASH one is not obvious at all. I would not close the issue until error message is extended mentioning this - e.g. suggesting extra-prog-path or just borrow whole PATH.
The text was updated successfully, but these errors were encountered: