From: Tom Lane <tgl@sss.pgh.pa.us>
To: arun007@pm.me
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18424: Build failure when static linking with openldap
In-reply-to: <18424-bc056c6239e511fd@postgresql.org>
References: <18424-bc056c6239e511fd@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sun, 07 Apr 2024 13:21:45 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2848763.1712504140.1@sss.pgh.pa.us>
Date: Sun, 07 Apr 2024 11:35:40 -0400
Message-ID: <2848764.1712504140@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2848764.1712504140%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Static linking openldap results in failure with the following error:
>  libpq.so.5.16:                 U pthread_exit@GLIBC_2.2.5
> libpq must not be calling any function which invokes exit

[ shrug... ]  So don't do that.  Statically linking libraries from
different sources is a pretty evil idea anyway, because it makes
package updates much harder.

Having said that, if you're hacking the makefiles enough to make
the link static, you can surely find and remove that check.  Just
don't expect us to take a patch to that effect.

			regards, tom lane