commercialhaskell/stack

stack doesn't find a shared object/dynamic library

Open

#2,299 opened on Jun 23, 2016

View on GitHub
 (16 comments) (2 reactions) (0 assignees)Haskell (4,060 stars) (848 forks)batch import
component: Windowsfurther investigation requiredhelp wanted

Description

(a similar scenario: #1974) I'm building a project using wxHaskell with wx, wxc, wxcore and wxdirect as extra-deps in my stack.yaml. The project builds fine on Linux and Windows and stack exec works right on Linux, however, on Windows it's complaining about a missing wxc.dll: The program can't start because wxc.dll is missing from your computer. stack ghci fails on both Linux and Windows, with the same message on Windows and the following error on Linux:

<command line>: can't load .so/.DLL for: .../lib/x86_64-linux-ghc-7.10.3/wxcore-0.92.2.0-FbIxJ6t4QQeCNL8GzPaZRM/libHSwxcore-0.92.2.0-FbIxJ6t4QQeCNL8GzPaZRM-ghc7.10.3.so (libwxc.so: cannot open shared object file: No such file or directory)

On both systems, the .so/.dll was present, located at .stack-work/install/x86_64-linux/../lib/x86_64-linux-ghc-7.10.3/wxc-0.92.2.0-.. and when I copied them to the current directory, where the command is called, everything went smoothly. I would expect stack to handle those cases.

(Note: the solution mentioned in #467 doesn't work)

Contributor guide

Tech stack
None
Domain
build systemcli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Haskell and Stack basicsDynamic linking conceptsWindows and Linux development setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate how stack resolves shared library paths for extra deps. Look at the stack source code for library path handling, particularly on Windows and Linux. Refer to similar issue #1974 and #467. Consider adding logic to automatically include library paths from extra deps into the runtime library search path (e.g., LD LIBRARY PATH or PATH on Windows). Test with wxHaskell project.