-
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
stack ghci ignores flags in stack.yaml and uses package.cabal defaults #5434
Labels
Comments
liskin
added a commit
to liskin/dotfiles
that referenced
this issue
Nov 15, 2020
This triggers a bug in stack (commercialhaskell/stack#5434) whenever I run ghcid, drop it for now. This reverts commit c4a8d86.
@liskin many thanks for open a different issue, with so many details. |
Thanks for the excellent write-up @liskin 👍 |
2 tasks
snoyberg
added a commit
that referenced
this issue
Aug 9, 2021
FIX #5434: use stack.yaml's package flags in stack ghci
hololeap
pushed a commit
to hololeap/stack
that referenced
this issue
Jan 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Minimal example:
This results in
With
./stack-2.5.1-linux-x86_64/stack --stack-root "$PWD"/.stack --system-ghc ghci --flag bug:someflag bug:lib
it works just fine.Adding
-v
reveals that-DBUG
isn't passed to ghci either. Do note that my expected behaviour is not that Bug2 wouldn't be loaded. My expected behaviour is that the ghci is invoked with-DBUG
and-package-id=containers-…
, so that I can use ghci and ghcid with the flags that I set in stack.yaml.Now here's a non-minimal real life example, just to show that this is actually reproducible with a real project, that perhaps some of you folks use and love:
This fails with:
Stack version
It's also reproducible with stack 2.3.3 from Debian.
Method of installation
The rest of the system is Debian testing on amd64 with ghc 8.8.4.
The text was updated successfully, but these errors were encountered: