Apple M1 and libgcrypt 1.9.2
noloader at gmail.com
Thu Mar 25 04:16:18 CET 2021
On Wed, Mar 24, 2021 at 3:31 PM Marius Schamschula
<lists at schamschula.com> wrote:
> On Mar 24, 2021, at 1:17 PM, Werner Koch <wk at gnupg.org> wrote:
> On Wed, 24 Mar 2021 13:03, Jeffrey Walton said:
> Until you have to autoreconf and the tools are missing or too old...
> In GnuPG project you should never do autoreconf. We distribute the
> required files for running autoconf and automake. This way we get a
> stable config system which is not suject to all the friction metween
> different macro use.
> Regarding M1, if you config.sub has stable support for it, we should
> update these files and then see what other fixes are required. In
> genera; autoconf generated configure scripts auto-adjust to a wide
> variety of Unix systems and you only need to tweak things for some minor
> cases - well, Apple is probably the worst player here.
> Having said this, I just ask for some patience and until we support it.
> Quick hacks are of course okay - it is free software. Unfortunately
> they have a tendency to never go away and still show up in web searches
> after years
> However, running autoreconf does make patching the configure script unnecessary.
> In other words, the macros used to build the packaged configure script are outdated.
I find fetching the latest config.sub and confg.guess, and overwriting
the tarball's files, is good maintenance. In fact, if you are building
the tarballs, it is a good idea to do, too.
The Gnulib folks even recommend using the latest config.sub and
confg.guess by fetching them using Wget:
More information about the Gnupg-devel