Re: [Haskell-cafe] GHC can't find DLL dependencies on Windows
Never mind, I figured it out. Previously, I had been placing C:\msys64\mingw64\bin at the end of my user PATH. It turns out that my PATH was in fact on the DLL search path, but for some reason, an earlier directory on my PATH was causing problems. I can't exactly pinpoint what was causing the problem, but after moving C:\msys64\mingw64\bin to the start of my system PATH, I can run Haskell executables in PowerShell/cmd.exe without a problem. Ryan S.
hi Ryan, As i fought the same battle recently, i will point out one related thing: If you plan to deploy your program, and copy the necessary dlls along with it, there can be a strange issue if you miss to copy some dependencies that are present (with a different version) on the target system. (presumably they were present due to a ghc install, but i have not investigated that part). The error was "The procedure entry point pthread_cond_timedwait_relative_np could not be located [..]" when trying to run the compiled executable. Fixed by including more of the msys/mingw64/bin dlls. I had tried to determine the dependencies with a different tool; maybe cygcheck does a better job so this won't arise. Just thought i'd let you know as i found this annoying to diagnose (and the googles don't help much). Lennart On 29/10/15 00:19, Ryan Scott wrote:
Never mind, I figured it out. Previously, I had been placing C:\msys64\mingw64\bin at the end of my user PATH. It turns out that my PATH was in fact on the DLL search path, but for some reason, an earlier directory on my PATH was causing problems. I can't exactly pinpoint what was causing the problem, but after moving C:\msys64\mingw64\bin to the start of my system PATH, I can run Haskell executables in PowerShell/cmd.exe without a problem.
Ryan S. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
On 29/10/15 00:19, Ryan Scott wrote:
Never mind, I figured it out. Previously, I had been placing C:\msys64\mingw64\bin at the end of my user PATH. It turns out that my PATH was in fact on the DLL search path, but for some reason, an earlier directory on my PATH was causing problems. I can't exactly pinpoint what was causing the problem, but after moving C:\msys64\mingw64\bin to the start of my system PATH, I can run Haskell executables in PowerShell/cmd.exe without a problem.
Ryan S. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
participants (2)
-
lennart spitzner -
Ryan Scott