| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, walther(at)technowledgy(dot)de |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
| Date: | 2024-03-25 22:46:09 |
| Message-ID: | 443430b4-0c10-49f3-8c8a-e5e76602f309@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2024-03-25 22:51:09 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
| Previous Message | Bruce Momjian | 2024-03-25 22:35:06 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2024-03-25 22:51:09 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
| Previous Message | Bruce Momjian | 2024-03-25 22:35:06 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |