From: Tom Lane <tgl@sss.pgh.pa.us>
To: cc@cj3.cc
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18980: Unable to perform make due to inability to resolve a
 variety of Undefined symbols arm64
In-reply-to: <18980-24d1032166d8d17f@postgresql.org>
References: <18980-24d1032166d8d17f@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 07 Jul 2025 21:04:15 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <585097.1751924857.1@sss.pgh.pa.us>
Date: Mon, 07 Jul 2025 17:47:37 -0400
Message-ID: <585098.1751924857@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/585098.1751924857%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Although I was able to compile and link 18beta1 source code on a very old
> mid-2010 iMac running MacOSX 10.13.6 [High Sierra], I could NOT compile and
> link PostgreSQL version 18beta1 source on my new M4 Pro Mac Book Pro running
> Mac OS Tahoe; *** also failed to compile and link on this same machine
> running Mac OS 15.5***

That does work for me, and for quite a few other people.

> Errors resulting from attempting to perform a make on PostgreSQL version
> 18beta1 look like:
> 177 Undefined symbols for architecture arm64:
> 178   "_ASN1_INTEGER_to_BN", referenced from:
> 179       _verify_cb in be-secure-openssl.o
> 180       _be_tls_get_peer_serial in be-secure-openssl.o
> 181   "_ASN1_STRING_print_ex", referenced from:
> 182       _X509_NAME_to_cstring in be-secure-openssl.o

All of these missing symbols seem to be from OpenSSL, which I don't
understand because your configure command didn't say --with-openssl.
Are you sure that's actually the full set of options you're using?
Maybe you have a stale autoconf cache you need to clean out?

If you are using --with-openssl, I wonder which OpenSSL you are
using.  Apple deprecated their system-library version of that
long ago, and perhaps it's finally gone in Tahoe.  Most of us
use Homebrew or MacPorts to install a version of the openssl
libraries that we can use with PG.  If you are trying to do it
like that, I think the problem is that you're missing --with-includes
and --with-libs configure options to point at that installation.
For instance, I use

  --with-includes=/opt/local/include --with-libs=/opt/local/lib

to build with MacPorts' openssl.

			regards, tom lane