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

Changing resolver from lts-5.11 to lts-6.1 triggers "Missing build tools" error #2235

Closed
chreekat opened this issue Jun 4, 2016 · 3 comments

Comments

@chreekat
Copy link
Member

chreekat commented Jun 4, 2016

Snowdrift at eabedbd builds fine. If I change to using lts-6.1, however, I get the error that mentions #595 (reproduced below).

$ stack build
No packages found in snapshot which provide a "hsc2hs" executable,
which is a build-tool dependency of "skein". Missing build-tools may be
caused by dependencies of the build-tool being overridden by
extra-deps. This should be fixed soon - see this issue
https://github.com/commercialhaskell/stack/issues/595

No packages found in snapshot which provide a "hsc2hs" executable,
which is a build-tool dependency of "postgresql-libpq" Missing
build-tools may be caused by dependencies of the build-tool being
overridden by extra-deps. This should be fixed soon - see this issue
https://github.com/commercialhaskell/stack/issues/595

While constructing the BuildPlan the following exceptions were
encountered:

--  Failure when adding dependencies:
      hjsmin: needed (>=0.1 && <0.2), 0.2.0.1 found (latest applicable is 0.1.5.3)
    needed for package Snowdrift-0.1.4 with flags:
      dev: True
@sigrlami
Copy link

Noticed this in docker when moved from 5.15 to 6.5, local build doesn't bring this error

@chreekat
Copy link
Member Author

Update: the error about hsc2hs is spurious. There's nothing wrong with it. The actual error preventing the build was at the bottom: Snowdrift.cabal needed to relax its restriction on hjsmin.

I think the issue still stands, but it is about spurious errors.

@mgsloan
Copy link
Contributor

mgsloan commented Nov 11, 2016

I've fixed this - it now checks if the tool is on the PATH before warning.

@mgsloan mgsloan closed this as completed Nov 11, 2016
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

3 participants