2009/3/31 Peter Verswyvelen
Maybe GHCi has a bug when it comes to DLL lookup. I had an application that worked fine when compiled with GHC, but failed with GHCi (libglew.dll not found) I used procmon to monitor which files the GHC* processes searched, and it seemed that the compiled version looked for libglew32.dll, while GHCi was looking for libglew.dll Since this only happened with our own wrapper project, I thought we made a mistake, but maybe you could also use procmon to figure out what GHCi is doing, it might be a bug.
ghci has a custom linker which behaves differently from gnu ld, which is what ghc uses. I don't recall the exact details (if I ever knew them), just that it differs. So something that works with ghc won't necessarily do so with ghci. Alistair