Paul Eggert wrote: > On 03/22/2013 09:31 AM, Jim Meyering wrote: > >> Network connectivity? > > Yes, that's what it was. A corrupted DNS cache, apparently. > (Which leads me to wonder: how trustworthy is that part of > the build procedure, anyway? But moving on....)
Interesting point. But as you say, moving on... >> I haven't investigated that for some time, but thought it was >> due to my (personal) use of gettext that's a little older than the >> latest, in which I presume that offending macro use has been removed. > > Unfortunately it was more complicated than that. Even with a newer > gettext it installed macros from gettext 0.17. I fiddled with it > and the following patch fixed things for me. It may be a bit > belt-and-suspenders, in that it insists on 0.18.2 when that > might not strictly be necessary with the other changes I made, > but to some extent I quit while I was ahead. > > Subject: [PATCH] maint: update build procedure to recent gettext etc. > > * bootstrap.conf (gnulib_modules): Add vararrays. > (needed_gnulib_files, unnecessary_gettext_files): New vars. > (bootstrap_post_import_hook): New function, to implement these vars. > (excluded_files): Remove; 'bootstrap' no longer supports this. > Its function is now performed by unnecessary_gettext_files. > (buildreq): Update automake to 1.12.2, to avoid CVE-2012-3386. > * configure.ac (AM_GNU_GETTEXT_VERSION): Bump from 0.17 to 0.18.2, > to lessen the probability that we'll have outlandishly old files > during a build. > * m4/vararrays.m4: Remove from repository, as we now use the > gnulib version. Thank you for doing all that. With that, I'll plan to release tomorrow.
