X-Mailer: MIME-tools 5.507 (Entity 5.507)
Content-Transfer-Encoding: binary
X-RT-Interface: Web
X-RT-Original-Encoding: utf-8
MIME-Version: 1.0
Message-ID: <rt-4.4.4-36280-1605984459-41.8968-0-0@mit.edu>
In-Reply-To: <wn5XdtHYISBqJKi9n90l0VjWDAG8aaKZ9p9EL5hGFd4gXZewm0d9rB_dwlZwk59mrGDwoGQQ85v2hQMCdXk-xCnGgJWuHPNzkVoey0pMO6g=@protonmail.com>
Content-Type: text/html; charset="utf-8"
References: <wn5XdtHYISBqJKi9n90l0VjWDAG8aaKZ9p9EL5hGFd4gXZewm0d9rB_dwlZwk59mrGDwoGQQ85v2hQMCdXk-xCnGgJWuHPNzkVoey0pMO6g=@protonmail.com> <RT-Ticket-8968@mit.edu>
Content-Disposition: inline
RT-Send-CC:
Content-Length: 1634

<div>Thanks for this writeup.<br />
<br />
What goes wrong when trying to build with gcc?&nbsp; Although I prefer clang over gcc, I don&#39;t know if there&#39;s a great path forward here.&nbsp; autoconf (as a Gnu project) is unlikely to stop preferring gcc.&nbsp; There are thousands of autoconf-using source distributions, and for each one of them to add its own per-platform decisions about the default compiler would be inefficient and unreliable.<br />
<br />
Changing shlib.conf to use $(CC) -shared is probably good.&nbsp; I note that NetBSD uses&nbsp;LDCOMBINE=&#39;$(CC) -shared&#39; (no other flags); I don&#39;t know if there&#39;s a reason for the discrepancy with Linux platforms.<br />
<br />
I would ordinarily expect that if a platform implements libm functions in libc that it would leave behind a stub libm, since -lm has a long history.&nbsp; But a configure test is appropriate now that there is an example of a platform that chose not to do that.<br />
<br />
The PKINIT LibreSSL incompatibility comes about mainly because LibreSSL defines&nbsp;OPENSSL_VERSION_NUMBER to&nbsp;0x20000000L, essentially declaring itself to be OpenSSL 2.0, while having no interest in maintaining compatibility with OpenSSL&#39;s API changes (or even some of its pre-existing features, such as CMS).&nbsp; People have written PKINIT patches to work around this, but it&#39;s really inelegant, and the rough consensus has been to push back against LibreSSL&#39;s bad practice here rather than accept it.&nbsp;&nbsp;I think it would be reasonable for configure to detect whether libcrypto comes from LibreSSL and disable PKINIT.</div>