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
--enable-executable-dynamic not working on packages containing both lib and executables, makes installation problematic #1568
Comments
We use http://nixos.org/patchelf.html to work around this kind of problem in NixOS. It's not pretty, but it works until there's a better solution. |
I'm facing the same issue on Haiku (ran into the example of pandoc in the linked email thread actually!). We'll be looking into the issue ourselves, so hopefully will have a PR to send your way soon enough... |
I tried looking into this issue, but my experience with Haskell quickly become severely inept! However, would it suffice as a solution for an invocation of E.g. run the configure/build/install phase for the libraries; then repeat again for the executable? During the phase for the executable, cabal would then use the installed library rather than the inplace library. |
Before, RPATH handling was left to GHC. But this causes problems when a package contains both a Library section and an Executable section which depends on the library, and the executable is dynamically linked. See e.g. haskell#1568
Before, RPATH handling was left to GHC. But this causes problems when a package contains both a Library section and an Executable section which depends on the library, and the executable is dynamically linked. See e.g. haskell#1568
Is there some magic incantation I need to pass to Cabal to make this work? I've just downloaded pandoc sources from Hackage, and run:
And version of cabal:
I've just tried with Once OS support is added, do I need to change the global configuration to use relocatable builds, or can I get the RPATH handling for free without enabling relocatable builds? |
RPATH for executables is set to include the build location for the library and not the install location for the library. This results in the situation described in detail in this mail.
This makes it rather impossible to install this type of packages when linking dynamically.
The text was updated successfully, but these errors were encountered: