Skip to content

Assertion failed when running new-configure with --enable-tests or --enable-bench on Custom setups #4621

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

Closed
fgaz opened this issue Jul 23, 2017 · 2 comments

Comments

@fgaz
Copy link
Member

fgaz commented Jul 23, 2017

~/code/haskell/cabal[master]$ cabal new-configure --enable-tests   
'cabal.project.local' file already exists. Now overwriting it.
In order, the following would be built (use -v for more details):
Assertion failed
CallStack (from HasCallStack):
  assert, called at ./Distribution/Client/ProjectPlanning.hs:280:5 in main:Distribution.Client.ProjectPlanning
@fgaz fgaz self-assigned this Jul 23, 2017
@23Skidoo 23Skidoo changed the title Assertion failed when running new-configure with --ebnable-tests or --enable-bench on Custom setups Assertion failed when running new-configure with --enable-tests or --enable-bench on Custom setups Aug 11, 2017
@ezyang
Copy link
Contributor

ezyang commented Dec 31, 2017

FWIW, this seems to mean that new-configure on Cabal itself does not work. Whoops, didn't read the original ticket correctly

@ezyang
Copy link
Contributor

ezyang commented Jan 3, 2018

Fixed.

@ezyang ezyang closed this as completed Jan 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants