diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2024-09-29 14:48:16 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2024-11-30 17:02:13 +0100 |
| commit | 3bd9f92eae830c03ec6e37b1727d4b43052149eb (patch) | |
| tree | 9006ca87f94b7890edf2fc6f0a34498586982a23 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 445371f309a62e9107ad78fb3c65fff768efb43c (diff) | |
pkgsStatic.postgresql: fix build
The underlying problem was fixed as a side-effect of [1], for reasons
unknown to me. In the current state, it's enough to disable a few
breaking dependencies to make the build pass.
Note, that this builds the full package, including backend. However, the
backend is not working, yet: Loading shared modules, which PostgreSQL
heavily depends is still broken. Further, all binaries in the default
output, even client binaries such as psql, are currently dynamically
linked against libpq.so. While the current autoconf based build system
doesn't support changing this, this might be possible in the future with
meson.
However, not all is bad: Fixing the build allows using the static
libpq.a library, which is probably the one thing that most users want
from pkgsStatic.postgresql anyway.
Resolves #191920
[1]: 77977286d80c9bfb77cbf80989d41c59d66dccf8
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
