| From: | Wolfgang Walther <walther(at)technowledgy(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
| Date: | 2024-03-16 20:00:28 |
| Message-ID: | eff5b49b-3d34-4a5b-82e9-e2630b1da37d@technowledgy.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-03-16 20:10:56 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
| Previous Message | Andrew Dunstan | 2024-03-16 19:49:27 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Étienne BERSAC | 2024-03-16 20:00:29 | Re: REVOKE FROM warning on grantor |
| Previous Message | Andrew Dunstan | 2024-03-16 19:49:27 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |