Re: Regression tests fail with musl libc because libpq.so can't be loaded
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Wolfgang Walther <walther@technowledgy.de>
Cc: Thomas Munro <thomas.munro@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Christophe Pettus <xof@thebuild.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>
Date: 2024-03-22T00:19:48Z
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
Hi, On 2024-03-21 21:16:46 +0100, Wolfgang Walther wrote: > Right. The latter not only confuses musl, but also makes /proc/<pid>/environ > return garbage. This is also mentioned at the bottom of main.c, which has a > workaround for the specific case of UBSan depending on that. This is kind of > funny: Because we are relying on undefined behavior regarding the > modification of environ, we need a workaround for the > "UndefinedBehaviorSanitizer" - I guess by failing without this workaround, > it wanted to tell us something.. I don't think that's quite a fair description. Ubsan is basically doing undefined things itself, so it's turtles all the way down. > So summarizing: FWIW, independent of which fix we go with, I think we need a buildfarm animal using musl. Even better if one of the CI tasks can be made to use musl as well. Greetings, Andres Freund