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

stack build failed --aeson-1.1.2.0 #446

Closed
valdu02100 opened this issue Jan 10, 2020 · 10 comments
Closed

stack build failed --aeson-1.1.2.0 #446

valdu02100 opened this issue Jan 10, 2020 · 10 comments

Comments

@valdu02100
Copy link

valdu02100 commented Jan 10, 2020

Hi,

I'm trying to install duckling so I can use it for RASA.
I'm on OS X. I installed brew install pcre and made a copy of the git.

When running the sudo stack build command, I get this error message.

valentin@mbp-de-valentin duckling % sudo stack build --allow-different-user  
aeson   > configure
aeson   > Configuring aeson-1.1.2.0...
aeson   > build
aeson   > Building aeson-1.1.2.0...
aeson   > Preprocessing library aeson-1.1.2.0...
aeson   > [ 1 of 21] Compiling Data.Aeson.Types.Internal ( Data/Aeson/Types/Internal.hs, .stack-work/dist/x86_64-osx/Cabal-1.24.2.0/build/Data/Aeson/Types/Internal.o )
aeson   > [ 2 of 21] Compiling Data.Aeson.Types.Generic ( Data/Aeson/Types/Generic.hs, .stack-work/dist/x86_64-osx/Cabal-1.24.2.0/build/Data/Aeson/Types/Generic.o )
aeson   > [ 3 of 21] Compiling Data.Aeson.Parser.UnescapeFFI ( ffi/Data/Aeson/Parser/UnescapeFFI.hs, .stack-work/dist/x86_64-osx/Cabal-1.24.2.0/build/Data/Aeson/Parser/UnescapeFFI.o )
aeson   > [ 4 of 21] Compiling Data.Aeson.Parser.Unescape ( Data/Aeson/Parser/Unescape.hs, .stack-work/dist/x86_64-osx/Cabal-1.24.2.0/build/Data/Aeson/Parser/Unescape.o )
aeson   > [ 5 of 21] Compiling Data.Aeson.Parser.Internal ( Data/Aeson/Parser/Internal.hs, .stack-work/dist/x86_64-osx/Cabal-1.24.2.0/build/Data/Aeson/Parser/Internal.o )
aeson   > <command line>: can't load .so/.DLL for: /Users/valentin/.stack/snapshots/x86_64-osx/c3b392cc580865f2abbcd4cdfb327b7ec325e191d0f161ca2a0763dcafdcc275/8.0.2/lib/x86_64-osx-ghc-8.0.2/libHStime-locale-compat-0.1.1.3-KZ1jqNx8uhlHjmuPPj6V1Y-ghc8.0.2.dylib (dlopen(/Users/valentin/.stack/snapshots/x86_64-osx/c3b392cc580865f2abbcd4cdfb327b7ec325e191d0f161ca2a0763dcafdcc275/8.0.2/lib/x86_64-osx-ghc-8.0.2/libHStime-locale-compat-0.1.1.3-KZ1jqNx8uhlHjmuPPj6V1Y-ghc8.0.2.dylib, 5): REBASE_OPCODE_SET_SEGMENT_AND_OFFSET_ULEB has segment 2 which is not a writable segment (__LINKEDIT) in /Users/valentin/.stack/snapshots/x86_64-osx/c3b392cc580865f2abbcd4cdfb327b7ec325e191d0f161ca2a0763dcafdcc275/8.0.2/lib/x86_64-osx-ghc-8.0.2/libHStime-locale-compat-0.1.1.3-KZ1jqNx8uhlHjmuPPj6V1Y-ghc8.0.2.dylib)
            
--  While building package aeson-1.1.2.0 using:
      /Users/valentin/.stack/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_1.24.2.0_ghc-8.0.2 --builddir=.stack-work/dist/x86_64-osx/Cabal-1.24.2.0 build --ghc-options ""
    Process exited with code: ExitFailure 1
Progress 1/2
valentin@mbp-de-valentin duckling % 

I'm stuck at this point and can't find any solutions.
Thank you for your help

@googlx
Copy link

googlx commented Jan 15, 2020

I also got this problem, any solution?

@googlx
Copy link

googlx commented Jan 15, 2020

I also got this problem, any solution?

I tried to remove the default yaml file(stack.yaml), and then run stack build again, it worked. 😃

@Brokray
Copy link

Brokray commented Mar 10, 2020

Hello, I am having the exact same problem as @valdu02100 and have tried @googlx's answer with no success.
Does anyone have any idea about this ? 🤔

@timoffex
Copy link

Same problem!

@KvitnucaZahradka
Copy link

@googlx solution worked for me.

@Kaspazza
Copy link

Kaspazza commented May 13, 2020

I had the same problem, the solutions provided here was not working.
Changing resolver in stack.yaml to the newest version (resolver: lts-13.11), and adding allow-newer: true helped.

@chenguanda
Copy link

I tried to

  1. remove the default yaml file(stack.yaml)
  2. remove all file in ~/.stack
  3. run stack init
    stack change resolver in stack.yaml to the newest version (resolver: lts-13.11),
  4. run stack build
    it worked. 😃

@chessai
Copy link
Contributor

chessai commented Oct 16, 2020

This will just need an update to the resolver. See #540

@valdu02100
Copy link
Author

Hello,

My solution was to install docker with a duckling image.
It's really easy to use.
If you need a quick fix, I recommend it.

@chessai
Copy link
Contributor

chessai commented Nov 6, 2020

This should be fixed in master

@chessai chessai closed this as completed Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants