gnutls @3.6.15 Failed to configure gnutls: autoreconf failure

[nhchan]

Intalling gnutls failed with the following error message:

Error: Failed to configure gnutls: autoreconf failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gnutls/gnutls/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port gnutls failed

It initially showed up during an update, but after a lot of issues, I decided to try installing on a blank slate (i.e., just running sudo port install gnutls with no other ports installed on the machine). It installed a bunch a dependencies, but when it arrives at gnutls, it failed with the same error.

The main.log is attached.

Thanks!

[Schamschula (Marius Schamschula)]

It looks like autoreconf does not know that the doc variant is unselected.

I will need to further investigate.

[Schamschula (Marius Schamschula)]

It looks like trace mode does not hide gtkdocize during autoreconf. Thus, I never ran into this issue.

gtk-doc needs to be present for autoreconf to work, even for the -doc variant. That, on the other hand causes a possibly unneeded package to be installed.

I'm not sure if autoreconf is still needed at this point.

[Schamschula (Marius Schamschula)]

In 245fac5a0a7f461f710bf30383786d5e0c5bc344/macports-ports (master):

gnutls: don't use autoreconf

Closes: #62746

[ryandesign (Ryan Carsten Schmidt)]

Replying to Schamschula:

I'm not sure if autoreconf is still needed at this point.

It was originally added in 2013 because at that time the glibtool bundled with gnutls did not pass on the -stdlib flag, so builds would fail if we were building for a different stdlib than the default (e.g. with libc++ on Mac OS X 10.6-10.8).

Looking at the log now, I see that the -stdlib flag is being passed on, even without autoreconf, so I guess gnutls has updated its bundled glibtool to a fixed version since then.