You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
since this MRpostgresql-libpq has significantly changed how they find/register their native libpq dependency and haskell.nix seemingly no longer can find it.
I have a workaround to use locally which is just fix it myself (thanks for this feature)
However it would be very nice if everything did work, and i'm a little lost, so i'm looking for advice on where the fix should be.
The original code simply used to have extra-libraries: pq in the cabal file - which i can see hackage.nix maps to a postgresql dependency.
the new version instead has a new package which (as i read it) uses a setup: Configure to register the dependency from within the configure file.
At a guess hackage.nix has no clue about the Configure step's desire to have libpq before it's too late - which makes me think that it should still be in the postgresql-libpq-configure.cabal's extra-libraries
The text was updated successfully, but these errors were encountered:
dten
changed the title
postgresql-libpq 0.10.2.0 or higher won't build - where's the fault lie?postgresql-libpq 0.10.2.0 or higher won't build - where's the fix go?
Nov 12, 2024
More of a question really for now.
since this MR
postgresql-libpq
has significantly changed how they find/register their nativelibpq
dependency andhaskell.nix
seemingly no longer can find it.I have a workaround to use locally which is just fix it myself (thanks for this feature)
packages.postgresql-libpq-configure.components.library.libs = pkgs.lib.mkForce [ pkgs.postgresql ];
However it would be very nice if everything did work, and i'm a little lost, so i'm looking for advice on where the fix should be.
The original code simply used to have
extra-libraries: pq
in the cabal file - which i can see hackage.nix maps to apostgresql
dependency.the new version instead has a new package which (as i read it) uses a
setup: Configure
to register the dependency from within the configure file.At a guess hackage.nix has no clue about the Configure step's desire to have
libpq
before it's too late - which makes me think that it should still be in thepostgresql-libpq-configure.cabal
'sextra-libraries
The text was updated successfully, but these errors were encountered: