Re: Apple's ranlib warns about protocol_openssl.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Apple's ranlib warns about protocol_openssl.c
Date: 2021-12-31 01:03:54
Message-ID: 2559611.1640912634@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> I also see it on an m1 mini I got when building against openssl 3.

Huh, I wonder why I'm not seeing it.

> There is -no_warning_for_no_symbols in apple's ranlib. But perhaps
> there's another way around this:
> We have ssl_protocol_version_to_openssl() in both be-secure-openssl.c
> and fe-secure-openssl.c. Perhaps we should just move it to
> protocol_openssl.c?

Those functions have the same name, but not the same arguments,
so it'd take some refactoring to share any code.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message tanghy.fnst@fujitsu.com 2021-12-31 01:12:25 RE: Failed transaction statistics to measure the logical replication progress
Previous Message Andres Freund 2021-12-31 00:49:35 Re: Apple's ranlib warns about protocol_openssl.c