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

Christophe Pettus <xof@thebuild.com>

From: Christophe Pettus <xof@thebuild.com>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: Wolfgang Walther <walther@technowledgy.de>, Thomas Munro <thomas.munro@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>

Date: 2024-03-17T21:05:54Z

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 Mar 17, 2024, at 13:33, Andrew Dunstan <andrew@dunslane.net> wrote:
> 
> That seems a little shortsighted. If other libc implementations find it appropriate to have similar macros why should they be different?

It's a philosophical argument against checking for particular libc implementations instead of particular features.  I'm not unsympathetic to that argument, but AFAICT there's no clean way of checking for this by examining feature #defines.