-
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
--ghc-options
only takes a single option
#3315
Comments
Make --ghc-options and --ghcjs-boot-options take multiple args #3315
Done in 9e2bd40. |
Re-opening this. Here's what happened:
Note that any future fix to this should also consider the usecase in #3353. It is also worthwhile to take a look at how |
@mgsloan I would be glad, if you could tell, what the status of this is. |
@sclausen I think the proper steps forward were in the other issue #3353 (comment) . Copying what I said there: Actually, I think that this was never a problem for configure-options, just an issue when invoking ghci directly with multi-ghc-options. I noticed that the configuration parsing code for stack.yaml uses argument parsing for "ghc-options", when it probably shouldn't. So, steps would be:
Also, some stuff to make sure this doesn't regress:
|
@mgsloan thanks for the quick answer! |
See #4747 |
stack ghci --ghc-options multi args (fixes #3315)
When I try to build the optimised compiler, I am greeted with an error from stack: ``` stack build --jobs 4 --ghc-options "-O3 -fllvm" --flag juvix:incomplete-error Invalid option `-fllvm' Usage: stack build [TARGET] [--dry-run] [--pedantic] [--fast] .... ``` -fllvm is treated as an option to stack, and not as part of the --ghc-options flag. This is a known issue commercialhaskell/stack#3315, that apparently was fixed. I am running a more recent version of stack (2.5.1), but it still comes up as a problem. A solution to this is by using multiple --ghc-options flags: ``` stack build --jobs 4 --ghc-options "-O3" --ghc-options "-fllvm" --flag juvix:incomplete-error ```
From the comment here #758 (comment) :
Curiously, the documentation on the
argsOption
function that handles this mentions --ghc-options, but it isn't currently used:Fix is to use this for
ghc-options
and make sure it's also used for other similar options fieldsThe text was updated successfully, but these errors were encountered: