-
Notifications
You must be signed in to change notification settings - Fork 842
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
stack ghci: missing library #1700
Comments
Hi, thanks for the detailed report! I'm thinking this is likely the same issue as #970 . That is, Also related is #1656 , though that's about So, I think this is pretty well tracked by other tickets, except for one point: that the invocation of ghci does not pay attention to |
A GHC bug which is potentially related: https://ghc.haskell.org/trac/ghc/ticket/11042 Looks like the fix made it into GHC 8 |
This just bit me today. I can't |
Resolving this issue could be a simple matter of wrapping up that info as ghci options here Line 308 in 6f7871b
|
I think this may have been resolved for some time, after e11c78c I can't get those examples to build, so can't test with ghci. Please comment / reopen if not |
I am running stack Version 1.0.2, Git revision fa09a98 (3084 commits) x86_64, on Ubuntu 15.04.
When I run
stack ghci
in my project, I get the following output:This is for the bindings-hdf5 package (https://github.com/jwiegley/bindings-dsl/tree/master/bindings-hdf5). I believe this issue might have something to do with the fact that, on Ubuntu 15.04, the hdf5.h header file (which is included simply as
#include <hdf5.h>
) is not in any of the default include locations (/usr/include), but in a different location (/usr/include/hdf5/serial).stack build
only worked on this project by either adding the lineor
to the cabal file.
I have tried running
stack ghci -- -I/usr/include/hdf5/serial -L/usr/lib/x86_64-linux-gnu/hdf5/serial -lhdf5
, which generated the output:Am I approaching this the right way? I think this issue might be similar to #498, but it seems that the fix for #498 is already been merged, so this must be a different problem.
The text was updated successfully, but these errors were encountered: