Richard Purdie wrote:
> > We run autoreconf against most things.
> > ...
> > gettext 0.21.1:
> > ...
>
> The latter two look like they're as I'm missing the gnulib fixes to
> largefile.m4.
autoreconf is not supported in GNU gettext; there's a script 'autogen.sh'
instead.
When I run this script o
On Tue, 2023-03-28 at 09:03 -0700, Jim Meyering wrote:
> On Tue, Mar 28, 2023 at 7:23 AM Richard Purdie
> wrote:
> > I was able to work around the EGREP_TRADITIONAL issue by reordering
> > macros. The issue is conditional code blocks which mean
> > EGREP_TRADITIONAL was not set in some configure o
That's close enough, yes. You actually don't need the "else" though, it's
enough to isolate the first call to egrep:
% cat >configure.ac <<'EOF'
AC_INIT([test], [0])
AC_PROG_CPP
AC_PROG_EGREP
# uncomment to make this work on new autoconf
# m4_ifdef([_AC_PROG_EGREP_TRADITIONAL], [_AC_
On 2023-03-28, Zack Weinberg wrote:
> Can someone who understands the problem described at
> https://lists.gnu.org/archive/html/autoconf/2022-11/msg00129.html
> please construct a minimal, self-contained configure.ac that
> reproduces that problem? It is difficult for me to tell whether
> anythin
On 2023-03-28 08:21, Warren Young wrote:
Surely Solaris 10 (shipped in 2005) is relegated to the role of porting target,
getting nothing but a “dist” tarball?
Good point. I'll cc this to Dagobert Michelsen, who maintains the
Autoconf port for Solaris 10. Dagobert, are people still running
Au
Please don't top-post on this mailing list.
On Tue, Mar 28, 2023, at 12:12 PM, Frederic Berat wrote:
> Regarding EGREP, although I agree in principle this can be solved by
> using AS_CASE, I'd argue that the component actually required
> AC_PROG_EGREP. In principle, that should be enough, and requ
Can someone who understands the problem described at
https://lists.gnu.org/archive/html/autoconf/2022-11/msg00129.html
please construct a minimal, self-contained configure.ac that
reproduces that problem? It is difficult for me to tell whether
anything needs to be fixed in Autoconf from this repor
Hello,
Regarding EGREP, although I agree in principle this can be solved by using
AS_CASE, I'd argue that the component actually required AC_PROG_EGREP. In
principle, that should be enough, and requesting the user to know that
internally there may be some need for "_AC_PROG_EGREP_TRADITIONAL" that
On Tue, Mar 28, 2023 at 7:23 AM Richard Purdie
wrote:
> I was able to work around the EGREP_TRADITIONAL issue by reordering
> macros. The issue is conditional code blocks which mean
> EGREP_TRADITIONAL was not set in some configure option combinations
> leading to obtuse failures.
>
> Our testing
On Mar 28, 2023, at 01:15, Paul Eggert wrote:
>
> Solaris 10 has only Perl 5.8.4.
As one who has griped to various software projects in the past about breaking
compatibility with old versions of Perl, I sympathize, but I thought the
Autoconf Way is to build configure scripts on a modern system
I was able to work around the EGREP_TRADITIONAL issue by reordering
macros. The issue is conditional code blocks which mean
EGREP_TRADITIONAL was not set in some configure option combinations
leading to obtuse failures.
Our testing so far shows the following three sets of issues.
Macro ordering
Hello,
This one is rather unfortunate. I've seen a similar problem on multiple
packages, including make 4.4 (though not 4.4.1, so at least we can "simply"
update).
For now I also noticed rcs (5.10.1), gzip (1.12), ImageMagick (1:7.1.1.4)
with similar failures.
About 50% of the Fedora packages tha
On Tue, 2023-03-28 at 09:18 +0100, Richard Purdie wrote:
> On Tue, 2023-03-28 at 08:44 +0100, Richard Purdie wrote:
> > On Mon, 2023-03-27 at 08:38 -0700, Jim Meyering wrote:
> > > We're overdue for a new release, so here's a snapshot in preparation
> > > for that, which I want to call 2.73 (skippi
On Tue, 2023-03-28 at 08:44 +0100, Richard Purdie wrote:
> On Mon, 2023-03-27 at 08:38 -0700, Jim Meyering wrote:
> > We're overdue for a new release, so here's a snapshot in preparation
> > for that, which I want to call 2.73 (skipping 2.72). There has never
> > been an autoconf-2.72 release, yet
On Mon, 2023-03-27 at 08:38 -0700, Jim Meyering wrote:
> We're overdue for a new release, so here's a snapshot in preparation
> for that, which I want to call 2.73 (skipping 2.72). There has never
> been an autoconf-2.72 release, yet `git describe` now prints 2.72c and
> has been printing strings
On 2023-02-07 21:29, Jacob Bachmeyer wrote:
use Exporter;
-use Time::HiRes qw(stat);
use IO::File;
+# use sub-second resolution timestamps if available,
+# carry on with one-second resolution timestamps if that is all we have
+BEGIN { eval { require Time::HiRes; import Time::HiRes qw(stat) } }
16 matches
Mail list logo
