#600: Cabal should use -dynamic linking for executable when package configured --enable-shared ----------------------------+----------------------------------------------- Reporter: juhp | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Linux | ----------------------------+----------------------------------------------- Comment(by KrzysztofSkrzetnicki): Replying to [comment:1 juhp]:
Maybe {{{runghc configure --ghc-opt=-dynamic}}} is a workaround?
It might work, but not when TH is used. For example it fails for me: {{{ $ cabal install --ghc-option=-dynamic Resolving dependencies... Configuring slayer-0.3.1... Preprocessing library slayer-0.3.1... Preprocessing executables for slayer-0.3.1... Building slayer-0.3.1... [ 1 of 32] Compiling Slayer.MultilineQQ ( src/Slayer/MultilineQQ.hs, dist/build/Slayer/MultilineQQ.o ) [ 2 of 32] Compiling Slayer.Network.EmailAddr ( src/Slayer/Network/EmailAddr.hs, dist/build/Slayer/Network/EmailAddr.o ) [ 3 of 32] Compiling Slayer.Network.Mail ( src/Slayer/Network/Mail.hs, dist/build/Slayer/Network/Mail.o ) Loading package ghc-prim ... linking ... done. (... lots of packages ...) Loading package ffi-1.0 ... linking ... done. src/Slayer/Network/Mail.hs:1:0: Dynamic linking required, but this is a non-standard build (eg. prof). You need to build the program twice: once the normal way, and then in the desired way using -osuf to set the object file suffix. cabal: Error: some packages failed to install: slayer-0.3.1 failed during the building phase. The exception was: ExitFailure 1 }}} I have no idea if the patch specified above is going to work or not. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/600#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects