Failed to build connection-0.2.6. The failure occurred during the configure step.

[alexbiehl]

using cabal HEAD, on OSX, I get:

$ cabal new-build
Failed to build connection-0.2.6. The failure occurred during the configure step.
Build log (
/Users/alexbiehl/.cabal/logs/ghc-8.0.1/connection-0.2.6-cd4d2d49df9273cf9d6b957d6bfd35cace4f1e3d9e583d3b98947d1f533bfb0c.log
):
Configuring component lib from connection-0.2.6
cabal: The following package dependencies were requested
--dependency='x509-system=x509-system-1.6.4-e44e312bde6a317e91fbfafcd5d479ca85d331b6b9456e13d3f8205377a7028c'
however the given installed package instance does not exist.
cabal: Failed to build connection-0.2.6 (which is required by hunt-cli,
hunt-server-cli and others). See the build log above for details.

A quick look into the log reveals no further information, just repeated the message:

$ less /Users/alexbiehl/.cabal/logs/ghc-8.0.1/connection-0.2.6-cd4d2d49df9273cf9d6b957d6bfd35cace4f1e3d9e583d3b98947d1f533bfb0c.log
Configuring component lib from connection-0.2.6
cabal: The following package dependencies were requested
--dependency='x509-system=x509-system-1.6.4-e44e312bde6a317e91fbfafcd5d479ca85d331b6b9456e13d3f8205377a7028c'
however the given installed package instance does not exist.

I can't see why x509-system should be missing, or why it can't be installed. This is quite mysterious.

[23Skidoo]

Managed to reproduce with GHC 8.0.2:

$ cabal get bloodhound
$ cabal sandbox init && cabal install --only-dep --enable-tests
$ cabal configure --enable-tests
$ cabal build
[...]
<command line>: cannot satisfy -package-id aeson-0.11.2.1-B4zJgvAhVvJC40pFgLElOf
    (use -v for more information)

[23Skidoo]

Interestingly, doesn't seem to happen with 7.10.3. @alexbiehl, do you have a .ghc.environment-$VER file in the same directory? Try deleting it.

[ezyang]

If it is GHC environment's fault (shouldn't be, it's ghc-8.0.1 and we're not enabled for that), see also #4010

[alexbiehl]

I am using stock ghc-8.0.1. There is no environment file to delete.

[alexbiehl]

Sorry, I forgot this thread.

I am using stock 8.0.1, there are no ghc env files to delete.

Edward Z. Yang notifications@github.com schrieb am Fr., 21. Okt. 2016,
00:08:

If it is GHC environment's fault (shouldn't be, it's ghc-8.0.1 and we're
not enabled for that), see also #4010
#4010

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3993 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AByiif49_75T_B87GXzwTcz4uxl7u6Nmks5q1-ZtgaJpZM4KY1al
.

[ezyang]

I don't seem to be able to reproduce using new-build. Trying the sandbox approach.

[ezyang]

@23Skidoo I just can't reproduce this at all with f48e17b on Linux. @alexbiehl, what commit of Cabal HEAD are you on? @23Skidoo did you reproduce on Mac OS X?

[23Skidoo]

@ezyang Nope, I use Ubuntu 16.04. Maybe it got fixed in the meantime.

[ezyang]

Can you give it a try?

[23Skidoo]

Couldn't reproduce with GHC 8.0.1 and the snapshot of cabal-install HEAD I use (not sure which git commit ID that is).

[ezyang]

Unmilestoning. If we can repro I'll remilestone.

[jneira]

After 5 years i cant reproduce in windows, ghc-8.6.5 and a recent cabal head so i would close this one, feel free to reopen if you continue experiencing it