Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rlaMx-003Cl0-Pb for pgsql-bugs@arkaria.postgresql.org; Sat, 16 Mar 2024 20:11:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rlaMw-00HaOi-Dn for pgsql-bugs@arkaria.postgresql.org; Sat, 16 Mar 2024 20:11:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rlaMw-00HaOa-5D for pgsql-bugs@lists.postgresql.org; Sat, 16 Mar 2024 20:11:02 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rlaMt-004tpF-IU for pgsql-bugs@lists.postgresql.org; Sat, 16 Mar 2024 20:11:02 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 42GKAuxO3005970; Sat, 16 Mar 2024 16:10:56 -0400 From: Tom Lane To: Andrew Dunstan cc: Wolfgang Walther , PostgreSQL Bugs Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded In-reply-to: References: <2852940.1710599083@sss.pgh.pa.us> <443da167-ee01-47d2-9c83-105694b4cbd5@technowledgy.de> Comments: In-reply-to Andrew Dunstan message dated "Sat, 16 Mar 2024 15:49:27 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3005968.1710619856.1@sss.pgh.pa.us> Date: Sat, 16 Mar 2024 16:10:56 -0400 Message-ID: <3005969.1710619856@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan 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