-
Notifications
You must be signed in to change notification settings - Fork 18
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
Missing entry point libintl_gettext when postgresql-libpq is used from GHCi or Template Haskell on Windows #14
Comments
Thanks for the report, but I don't use Windows hardly at all. So I won't be able to offer much real help here. Although, you might want to read pull request #13; especially the link to a thread on an OpenBSD mailing list regarding this binding. Most interestingly, they suggested that we should be getting link options from It does seem less than likely that this would also fix these windows build problems, but you might find it useful nonetheless. Though I would like to know what the output of your I'm assuming this test works with older versions of libpq and/or older versions of GHC? |
It used to work with older versions of PostgreSQL. Here is my pg_config output:
I did find a workaround: put libintl.dll in the current directory. That is:
Doing these, I was able to build postgresql-simple and get the test suite to work. |
Is libintl a new dependency, introduced with libpq 9.3? |
On Windows 8 (64-bit), PostgreSQL 9.3 (32-bit), GHC 7.6.3 (32-bit), and Cabal 1.18.0.2 (32-bit), I get an error window when I
cabal install postgresql-simple
:I get the same error if I open ghci and run the following:
Compiling an executable does not produce this error. Only when it's interpreted (GHCi or Template Haskell) does this error come up.
I suspect GHC's flaky home-made linker is at fault. Hopefully this bug will go away when GHC 7.8 is released (which I hear will have better linker support). In the mean time, maybe there's some workaround that will get the dependencies of libpq.dll to load.
The text was updated successfully, but these errors were encountered: