Re: Regression tests fail with musl libc because libpq.so can't be loaded
Wolfgang Walther <walther@technowledgy.de>
From: Wolfgang Walther <walther@technowledgy.de>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>
Date: 2024-03-16T20:00:28Z
Lists: pgsql-bugs, pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Allow "make check"-style testing to work with musl C library.
- d82605bcd666 14.12 landed
- 8a92b70c11ba 17.0 landed
- 7651fd387697 16.3 landed
- 7124e7d528a8 12.19 landed
- 3c3f4fd741d0 15.7 landed
- 243e9953281f 13.15 landed
-
Fix compiler warnings on MSYS2
- 8c6d30f21139 13.0 cited
Andrew Dunstan: > On Alpine Linux, which uses musl libc, you have to run `make install` > before you can run `make check`. Have you tried that? I can see how that could work around the problem, because the library would already be available in the default library path / rpath and LD_LIBRARY_PATH would not be needed. However, this would only be a workaround for the specific case of running the regression tests, not a solution. Using LD_LIBRARY_PATH, as documented, would still not be possible. In my case, I am just using docker images with Alpine to easily reproduce the problem. I am building with NixOS / nixpkgs' pkgsMusl. The order of check and install phases can't be changed there, AFAICT. The workaround I use right now is to temporarily patch rpath of the postgres binary - this will be reset during the install phase anyway. This works, but again is not a real solution. Best, Wolfgang