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

Behavior when settings options via new-configure and new-build. #5457

AndreasPK opened this issue Jul 26, 2018 · 1 comment


None yet
1 participant
Copy link

commented Jul 26, 2018

The options of all of these flags apply only to local packages in a project; this behavior is different than that of cabal install.

'--with-PROG' and '--PROG-options' are applied to all packages
and not local packages only (#5019). Mikhail Glushenkov <> March 2018

This should be updated I assume if this behavior is here to stay.

There is also a bug where new-builds doesn't pick up options set via new-configure

  • new-configure --disable-tests --ghc-options="-fimpossible-flag" lists as far as I can tell all dependencies as being rebuilt. (So working like the changelog describes)
  • cabal new-build all --disable-tests --ghc-options="-fimpossible-flag" --dry-run does as well.
  • cabal new-configure <brokenFlag>; cabal new-build all --dry-run does ignore the broken flag change and thinks everything is up to date.

I guess configure is either writing a wrong project.local file or new-build is ignoring it.

$ cabal --version
cabal-install version
compiled using version of the Cabal library

This comment has been minimized.

Copy link
Contributor Author

commented Jul 31, 2018

This seems to be fixed in the master branch for what it's worth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.