On Thu, Jan 3, 2013 at 12:27 PM, Dawe <dawed...@gmx.de> wrote: > On Jan 03, 2013 11:55, David Coppa wrote: >> On Wed, Jan 2, 2013 at 10:26 PM, Dawe <dawed...@gmx.de> wrote: >> > Hi, >> > >> > I'm running the Dec. 21 amd64 snapshot with Dec. 29 packages. >> > >> > Trying to use hs-HDBC-postgresql-2.3.2.1p0 (from packages) or >> > postgresql-libpq >> > (via cabal install) in ghci ends in a linking failure similar to the >> > problems we >> > had back in october when ghc was updated. >> > A ghc-compiled binary that uses postgresql-libpq runs fine. >> > >> > I tried some other hs packages in ghci like hs-HDBC-mysql-0.6.6.0p0, >> > hs-HDBC-sqlite3-2.3.3.0p1 and hs-network-2.3.1.0 but they worked as >> > expected. >> > >> > I don't think the packages are to blame as they work in ghci on the ubuntu >> > of my >> > gf. >> > So, did someone else notice ghci linker problems since the workaround was >> > commited back in october? >> > Or is it possible, that the libpq.a archive is causing this? >> >> Hi! >> >> The attached diff should fix your problem. >> >> Thanks for your feedback. >> >> cheers, >> david > > Yes, it does :) > Thanks a lot for your quick help, really great! > Would you mind a short explanation why we have to add the extra libs and other > systems don't? >
Because on some platforms (like Linux) GHC has shared libraries support enabled, while this is not yet possible on OpenBSD. Sometimes upstream developers tend to abuse this feature...
