aeson-1.0.1.0 failed during the building phase. [ExitFailure 1] #469

Closed
mberlanda opened this Issue Sep 28, 2016 · 6 comments

Comments

Projects
None yet
4 participants
@mberlanda

I have some issues while installing the package with cabal.

The error backtrace is the following:

$ cabal install aeson
Resolving dependencies...
Configuring aeson-1.0.1.0...
Building aeson-1.0.1.0...
Preprocessing library aeson-1.0.1.0...
[ 1 of 20] Compiling Data.Aeson.Types.Generic ( Data/Aeson/Types/Generic.hs, dist/build/Data/Aeson/Types/Generic.o )
[ 2 of 20] Compiling Data.Aeson.Parser.Unescape ( Data/Aeson/Parser/Unescape.hs, dist/build/Data/Aeson/Parser/Unescape.o )
[ 3 of 20] Compiling Data.Aeson.Internal.Functions ( Data/Aeson/Internal/Functions.hs, dist/build/Data/Aeson/Internal/Functions.o )
[ 4 of 20] Compiling Data.Aeson.Internal.Time ( Data/Aeson/Internal/Time.hs, dist/build/Data/Aeson/Internal/Time.o )
[ 5 of 20] Compiling Data.Aeson.Types.Internal ( Data/Aeson/Types/Internal.hs, dist/build/Data/Aeson/Types/Internal.o )
[ 6 of 20] Compiling Data.Aeson.Encoding.Builder ( Data/Aeson/Encoding/Builder.hs, dist/build/Data/Aeson/Encoding/Builder.o )
[ 7 of 20] Compiling Data.Aeson.Encoding.Internal ( Data/Aeson/Encoding/Internal.hs, dist/build/Data/Aeson/Encoding/Internal.o )

Data/Aeson/Encoding/Internal.hs:201:40:
    No instance for (Semigroup Builder) arising from a use of `<>'
    Possible fix: add an instance declaration for (Semigroup Builder)
    In the first argument of `Encoding', namely `(a <> b)'
    In the expression: Encoding (a <> b)
    In an equation for `><':
        (Encoding a) >< (Encoding b) = Encoding (a <> b)

Data/Aeson/Encoding/Internal.hs:220:17:
    No instance for (Semigroup Builder) arising from a use of `<>'
    Possible fix: add an instance declaration for (Semigroup Builder)
    In the second argument of `($)', namely
      `char7 '"'
       <> LT.foldrChunks (\ x xs -> EB.unquoted x <> xs) (char7 '"') t'
    In the expression:
      Encoding
      $ char7 '"'
        <> LT.foldrChunks (\ x xs -> EB.unquoted x <> xs) (char7 '"') t
    In an equation for `lazyText':
        lazyText t
          = Encoding
            $ char7 '"'
              <> LT.foldrChunks (\ x xs -> EB.unquoted x <> xs) (char7 '"') t
Failed to install aeson-1.0.1.0
cabal: Error: some packages failed to install:
aeson-1.0.1.0 failed during the building phase. The exception was:
ExitFailure 1

Of course, I ran cabal update before trying to install your package.

  • Glasgow Haskell Compiler, Version 7.6.3, stage 2 booted by GHC version 7.6.3
  • using version 1.16.0 of the Cabal library
@phadej

This comment has been minimized.

Show comment
Hide comment
@phadej

phadej Sep 28, 2016

Contributor

Could you provide -v2 output?

Contributor

phadej commented Sep 28, 2016

Could you provide -v2 output?

@phadej

This comment has been minimized.

Show comment
Hide comment
@phadej

phadej Sep 28, 2016

Contributor

I tried locally:

bytestring-0.10.8.1 (new version)
binary-0.8.4.1 (new version)
dlist-0.8.0.2 (new package)
fail-4.9.0.0 (new package)
text-1.2.2.1 (new package)
hashable-1.2.4.0 (new package)
nats-1.1.1 (new package)
time-locale-compat-0.1.1.3 (new package)
transformers-0.5.2.0 (new package)
primitive-0.6.1.0 (new package)
transformers-compat-0.5.1.4 (new package)
tagged-0.8.5 (new package)
unix-2.7.2.0 (new version)
base-compat-0.9.1 (new package)
unordered-containers-0.2.7.1 (new package)
semigroups-0.18.2 -bytestring (new package)
vector-0.11.0.0 (new package)
scientific-0.3.4.9 (new package)
attoparsec-0.13.1.0 (new package)
aeson-1.0.1.0 (new package)

cabal-install-1.16 creates dumb plan, we cannot really do anything about. You have to use cabal-install >=1.18 to get good install plan unfortunately.

Contributor

phadej commented Sep 28, 2016

I tried locally:

bytestring-0.10.8.1 (new version)
binary-0.8.4.1 (new version)
dlist-0.8.0.2 (new package)
fail-4.9.0.0 (new package)
text-1.2.2.1 (new package)
hashable-1.2.4.0 (new package)
nats-1.1.1 (new package)
time-locale-compat-0.1.1.3 (new package)
transformers-0.5.2.0 (new package)
primitive-0.6.1.0 (new package)
transformers-compat-0.5.1.4 (new package)
tagged-0.8.5 (new package)
unix-2.7.2.0 (new version)
base-compat-0.9.1 (new package)
unordered-containers-0.2.7.1 (new package)
semigroups-0.18.2 -bytestring (new package)
vector-0.11.0.0 (new package)
scientific-0.3.4.9 (new package)
attoparsec-0.13.1.0 (new package)
aeson-1.0.1.0 (new package)

cabal-install-1.16 creates dumb plan, we cannot really do anything about. You have to use cabal-install >=1.18 to get good install plan unfortunately.

@bergmark

This comment has been minimized.

Show comment
Hide comment
@bergmark

bergmark Sep 28, 2016

Collaborator

Is there a fix for older cabals? Is it possible to solve by adding another constraint?

Collaborator

bergmark commented Sep 28, 2016

Is there a fix for older cabals? Is it possible to solve by adding another constraint?

@bergmark

This comment has been minimized.

Show comment
Hide comment
@bergmark

bergmark Oct 18, 2016

Collaborator

Unfortuntately I don't think there's anything we can do here, but if someone figures it out please let us know!

Collaborator

bergmark commented Oct 18, 2016

Unfortuntately I don't think there's anything we can do here, but if someone figures it out please let us know!

@bergmark bergmark closed this Oct 18, 2016

@23Skidoo

This comment has been minimized.

Show comment
Hide comment
@23Skidoo

23Skidoo Mar 3, 2017

Contributor

Had the same issue on GHC 7.8, nuking ~/.ghc/~/.cabal and rerunning cabal install aeson fixed it. Using cabal-install 1.24.

Contributor

23Skidoo commented Mar 3, 2017

Had the same issue on GHC 7.8, nuking ~/.ghc/~/.cabal and rerunning cabal install aeson fixed it. Using cabal-install 1.24.

@bergmark

This comment has been minimized.

Show comment
Hide comment
@bergmark

bergmark Mar 3, 2017

Collaborator

I forgot that this issue existed and reported the same thing @ haskell-infra/hackage-trustees#92 which we closed for the same reason... i'll re-open it.

Collaborator

bergmark commented Mar 3, 2017

I forgot that this issue existed and reported the same thing @ haskell-infra/hackage-trustees#92 which we closed for the same reason... i'll re-open it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment