Skip to content
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 new-install doesn't support --ghc-options #5788

Closed
hasufell opened this issue Dec 10, 2018 · 5 comments · Fixed by #5931
Closed

cabal new-install doesn't support --ghc-options #5788

hasufell opened this issue Dec 10, 2018 · 5 comments · Fixed by #5931

Comments

@hasufell
Copy link
Member

$ cabal new-install --ghc-options='-fllvm -optlo-O2 -j +RTS -A64m -n2m -RTS' all
cabal: unrecognized 'new-install' option `--ghc-options=-fllvm -optlo-O2 -j
@ip1981
Copy link

ip1981 commented Dec 11, 2018

Works with

# cabal --version
cabal-install version 2.2.0.0
compiled using version 2.2.0.1 of the Cabal library

@hasufell
Copy link
Member Author

So it seems this is a regression then

@Mistuke
Copy link
Collaborator

Mistuke commented Dec 16, 2018

Yes I just came here to report this as well. I don't see anything in the changelog so must be a regression.
It's quite a significant one though as it makes reducing GHC problems quite a lot harder.

Any idea what changed here /cc @hvr @23Skidoo ?

@typedrat
Copy link
Collaborator

That's very strange, and doesn't seem to be CmdInstall.hs related, since the only change was the addition of new options, not anything that should make old ones go away.

@hvr
Copy link
Member

hvr commented Dec 17, 2018

@typedrat another change from 2.2 to 2.4 I see in new-install --help is that the --hadock-* options lost their haddock- prefix; this is quite confusing as this means we get flags such as

    --for-hackage                                        Collection of flags to
                                                         generate documentation
                                                         suitable for upload to
                                                         hackage
    --executables                                        Run haddock for Executables
                                                         targets
    --tests                                              Run haddock for Test Suite
                                                         targets
    --benchmarks                                         Run haddock for Benchmark
                                                         targets
    --foreign-libraries                                  Run haddock for Foreign
                                                         Library targets
    --all                                                Run haddock for all targets
    --internal                                           Run haddock for internal
                                                         modules and include all
                                                         symbols
    --css=PATH                                           Use PATH as the haddock
                                                         stylesheet
    --hyperlink-source                                   Hyperlink the documentation
                                                         to the source code
    --quickjump                                          Generate an index for
                                                         interactive documentation
                                                         navigation

@hvr hvr added the type: bug label Dec 17, 2018
harpocrates added a commit to harpocrates/cabal that referenced this issue Mar 10, 2019
See further discussion in haskell#5788. Basically, `v2-install` currently
supports Haddock options, but in their unprefixed form. This is
unexpected and somewhat jarring.
harpocrates added a commit to harpocrates/cabal that referenced this issue Mar 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants