From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Wolfgang Walther <walther@technowledgy.de>
Cc: PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
Date: Sat, 16 Mar 2024 16:10:56 -0400
Message-ID: <3005969.1710619856@sss.pgh.pa.us> (raw)
In-Reply-To: <CAD5tBcJ7r_g1gUCp63ugjE6doz_Fu_1VJQJ5Cz_gLGKJ3e1Ktg@mail.gmail.com>
References: <fddd1cd6-dc16-40a2-9eb5-d7fef2101488@technowledgy.de>
<2852940.1710599083@sss.pgh.pa.us>
<443da167-ee01-47d2-9c83-105694b4cbd5@technowledgy.de>
<CAD5tBcJ7r_g1gUCp63ugjE6doz_Fu_1VJQJ5Cz_gLGKJ3e1Ktg@mail.gmail.com>
Andrew Dunstan <andrew@dunslane.net> writes:
> On Alpine Linux, which uses musl libc, you have to run `make install`
> before you can run `make check`. Have you tried that?
We have the same situation on macOS. There, it seems to be the result
of a "security feature" that strips DYLD_LIBRARY_PATH from the process
environment when make executes a shell. There's not much we can do
about that, and I suspect there is not much we can do about musl's
behavior either. (I am not a fan of proposals to modify the binaries
under test, because then you are not testing what you intend to
install.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, walther@technowledgy.de, pgsql-bugs@lists.postgresql.org
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
In-Reply-To: <3005969.1710619856@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox