Re: Regression tests fail with musl libc because libpq.so can't be loaded

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Bruce Momjian <bruce@momjian.us>, walther@technowledgy.de

Cc: Thomas Munro <thomas.munro@gmail.com>, Christophe Pettus <xof@thebuild.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>

Date: 2024-03-25T22:46:09Z

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

On 22.03.24 20:44, Bruce Momjian wrote:
> +				 * linking (dlopen) might fail.  Here, we truncate the update
> +				 * of the process title when either of two important dynamic
> +				 * linking environment variables are set.  Musl does not
> +				 * define any compiler symbols, so we have to do this for
> +				 * any Linux libc we don't know is safe.
> +				 */
> +				if (strstr(environ[i], "LD_LIBRARY_PATH=") == environ[i] ||
> +					strstr(environ[i], "LD_PRELOAD=") == environ[i])

What determines which variables require this treatment?