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 1rlxCl-0057hO-ST for pgsql-bugs@arkaria.postgresql.org; Sun, 17 Mar 2024 20:34: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 1rlxCi-00Cs8I-7L for pgsql-bugs@arkaria.postgresql.org; Sun, 17 Mar 2024 20:34:00 +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 1rlxCh-00Cs89-RC for pgsql-bugs@lists.postgresql.org; Sun, 17 Mar 2024 20:34:00 +0000 Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rlxCb-0054AA-Mh for pgsql-bugs@lists.postgresql.org; Sun, 17 Mar 2024 20:33:59 +0000 Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2d485886545so54375121fa.2 for ; Sun, 17 Mar 2024 13:33:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dunslane-net.20230601.gappssmtp.com; s=20230601; t=1710707631; x=1711312431; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=G3NNus3jsr1kgPOgBfOwPeNBJGlTPzdnSW+FoLY4ZIM=; b=T0qzJkOTaAcHa7sLnMynRj6P5HbYs7fX/JeA7Q4bKEyF7eMZEsutIRWHIwY/20OnxM qvEXzZ/p62PDdv+nsaomoQD4Znw7HU/pDy9gdCe/0LTZXhPwQr5W8D5e4rNAbGmueRtY nLkDr/AVfucHrqoC6uH4oaVJgprCurRx6VUxknZ4K2wOyMw+ePiVPpBwOjr7f7OIQSCw gG1odJbYyEk7TxwAz+GaMVYzAKUZqHSUdLSQTo8iWGvutJYhseJgQ5W4SChD5DzxvcBl 5qaO6/d4nxUY7WkpmfwAWIXl8BVoW5qgiqbCXZKMi2QsYqx6VEYvHcPvEpA/+w0CU3CQ gYbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710707631; x=1711312431; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=G3NNus3jsr1kgPOgBfOwPeNBJGlTPzdnSW+FoLY4ZIM=; b=I7jy3PCEG0JT6MuNasgwxU/gVRt/ZC5WNfzc9r6mqGJjcNSkLAbJRFu5y3wNdetsg/ RyVao6Onksxq28pmD0FLNBeJp4TblDrxIRoGGiYh+IWYiVxItCGMSWzMf084tUBzh7f/ TLPSrIURLYAjkdEQz9V1BSZWau3zkYj8yANM8B86p57zOCdnBanoc0NhkCeBLN9ksf4M /qei8ZQynD1QOqYZhDCCDnGsdI/5HxNyy+8/EQ9KMKMWrHaUJuwylp6+2DD6K4Uvr6E+ 8koM6/ruIU/Vei3ugTJjOM09tekBzHn31E8Y1b3/qcyC815dJIU1DpCcO597d8PMEcsg PxdQ== X-Forwarded-Encrypted: i=1; AJvYcCX277SlREGRW0X/w7MAskPS1Q8OZBt/sppk147pYSuQavr8aTYxUIu7ZS2NT7xOPJmcWea90hK/PQYvIzDWNoWfGElVClUuacLn7ffYqCBr X-Gm-Message-State: AOJu0YzR5SbS1F/JmGQq9GG1vk7kpzihwoYMJptD6vuIacv9XRy5n5bv q91mkc+uaHLRnrR+Fxu+VLJg5zJOq0m5/LEh6Rfz3Wg7vIDBbap65aqrOk7QL6vjseyFgLyRpp6 jkO2+AgMTTpBujL6SQ75RQUjJXE76sNU0aglMtQ== X-Google-Smtp-Source: AGHT+IHzkh1JWuTMpz55CbJVraTksNPekBQok6471PUWRX8CyLBYCRn1LIaMbeO0sUhfjhB0XGcPOnSSh+AhRHMF69U= X-Received: by 2002:a19:ca48:0:b0:513:e643:cd12 with SMTP id h8-20020a19ca48000000b00513e643cd12mr1852961lfj.26.1710707631399; Sun, 17 Mar 2024 13:33:51 -0700 (PDT) MIME-Version: 1.0 References: <2852940.1710599083@sss.pgh.pa.us> <443da167-ee01-47d2-9c83-105694b4cbd5@technowledgy.de> <68C88EE3-CDCB-4993-9173-3A773F491F3A@thebuild.com> <855a1b16-0dc0-42b2-8f90-79eb49cf2893@technowledgy.de> In-Reply-To: From: Andrew Dunstan Date: Sun, 17 Mar 2024 16:33:40 -0400 Message-ID: Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded To: Christophe Pettus Cc: Wolfgang Walther , Thomas Munro , Tom Lane , PostgreSQL Bugs Content-Type: multipart/alternative; boundary="000000000000af4aa20613e12855" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000af4aa20613e12855 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Mar 17, 2024 at 11:45=E2=80=AFAM Christophe Pettus wrote: > > > > On Mar 17, 2024, at 06:11, Wolfgang Walther > wrote: > > The missing macro is on purpose and unlikely to change: > https://openwall.com/lists/musl/2013/03/29/13 > > Indeed. > That seems a little shortsighted. If other libc implementations find it appropriate to have similar macros why should they be different? > > I also found this thread, which discusses exactly our case: > https://www.openwall.com/lists/musl/2022/08/17/1 > > While getting proper setproctitle functionality on musl would be great, m= y > goal was more modest: Have it correctly set PS_USE_NONE when compiling > against musl. > One simple thing might be for us to enclose the block in ps_status.c at lines 49-59 in #ifndef PS_USE_NONE/#endif. Then you could compile with -DPS_USE_NONE in your CPPFLAGS. cheers andrew --000000000000af4aa20613e12855 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Mar 17, 2024 at 11:45=E2=80= =AFAM Christophe Pettus <xof@thebuil= d.com> wrote:


> On Mar 17, 2024, at 06:11, Wolfgang Walther <walther@technowledgy.de> wrot= e:
> The missing macro is on purpose and unlikely to change: https://openwall.com/lists/musl/2013/03/29/13

Indeed.

That seems a little shortsighte= d. If other libc implementations find it appropriate to have similar macros= why should they be different?=C2=A0


> I also found this thread, which discusses exactly our case: https://www.openwall.com/lists/musl/2022/08/17/1

While getting proper setproctitle functionality on musl would be great, my = goal was more modest: Have it correctly set PS_USE_NONE when compiling agai= nst musl.

One simple thing might be for= us to enclose the block in ps_status.c at lines 49-59 in #ifndef PS_USE_NO= NE/#endif. Then you could compile with -DPS_USE_NONE in your CPPFLAGS.
=

cheers

andrew
<= /div>
--000000000000af4aa20613e12855--