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 does not fail on non-existing system build-tools #5464

Open
sol opened this issue Jul 29, 2018 · 2 comments
Open

Cabal does not fail on non-existing system build-tools #5464

sol opened this issue Jul 29, 2018 · 2 comments
Assignees

Comments

@sol
Copy link
Member

sol commented Jul 29, 2018

Since Cabal >= 2.0 it is possible to list arbitrary executables as build-tools. According to the documentation those executables need to be on the PATH. However, cabal will silently ignore non-existing executables.

hspec/hspec-example@512125d demonstrates the issue.

Steps to reproduce:

$ cabal --version
cabal-install version 2.2.0.0
compiled using version 2.2.0.1 of the Cabal library
$ git clone -b build-tools-bug https://github.com/hspec/hspec-example/
$ cd hspec-example
$ cabal new-test

Expected behavior: cabal complains about the missing build tool

Actual behavior: cabal runs the test suite

@hvr
Copy link
Member

hvr commented Jul 29, 2018

cc'ing @Ericson2314 who might be familiar with the issue

@Ericson2314
Copy link
Collaborator

We should have soem sort explicit "foreign/system build tool depends" thing to desugar unknown build-tools into. That is the last step to build-tools being 100% desugared and deprecated. The fact that it is so close but not quite is probably the source of this bug.

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

4 participants