[sr #111238] downstream package build failure with autoreconf+gettext-0.24.1

Zack Weinberg <[email protected]> Tue, 27 Jan 2026 11:58:21 -0500 (EST)
Newsgroups gmane.comp.sysutils.autoconf.bugs
Message-ID <[email protected]>
Update of sr #111238 (group autoconf):

                  Status:               Confirmed => Done
             Open/Closed:                    Open => Closed

    _______________________________________________________

Follow-up Comment #9:

I *believe* that the actual problem encountered by the original reporter of
this issue should be fully addressed by commits
f0d97fb5999427e41ed76f9d20451da392c03d27 and
4774e6bb311b95ed018150ff1d5b62056f2bc75e.  If issues still remain with the
interaction between autoreconf and current versions of gettext, please file a
new bug report.

The question of what autoreconf's scope should actually be, and the question
of how redistributors of software using autoconf should handle the
long-standing difference between what's in the VCS and what's in an
autotools-generated tarball, are probably best discussed on the mailing lists,
not here.  I don't have time to lead such a discussion at present.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?111238>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaXjurQAKCRCqLAuaBUf3
TnUMAQD//ViyoIASQD/rXNY+XKx3p8FuwIpdtQzcWmFsrP5ngwD+NnFktpCK9Gis
iIOlB7AcAakx5fUk/oHoxSQ4ai7eVgQ=
=/m69
-----END PGP SIGNATURE-----