URL:
<https://savannah.gnu.org/support/?110503>
Summary: Autoconf 2.70 regression: gkt-doc/gtkdocize is now
unconditionally required
Project: Autoconf
Submitted by: epirat
Submitted on: Tue 01 Jun 2021 09:51:46 PM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: None
_______________________________________________________
Details:
Autoconf introduced a new feature for autoreconf in 2.70:
> *** autoreconf will now run gtkdocize and intltoolize when appropriate.
This has the side-effect of making the gtkdocize tool required unconditionally
even for projects that follow the official documentation
<https://developer.gnome.org/gtk-doc-manual/stable/settingup_autoconf.html.en>
(Example 2-3):
# check for gtk-doc
m4_ifdef([GTK_DOC_CHECK], [
GTK_DOC_CHECK([1.14],[--flavour no-tmpl])
],[
AM_CONDITIONAL([ENABLE_GTK_DOC], false)
])
Projects that use this snippet nevertheless now fail to autoreconf properly
with the following error:
> Can't exec "gtkdocize": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
> autoreconf: error: gtkdocize failed with exit status: 2
Ideally autoreconf should detect if GTK_DOC_CHECK is checked with m4_ifdef and
not require gtkdocize in this case. If thats too complex, possibly it could
never require gtkdocize and only warn if its missing but looks like it might
be needed?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110503>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
