* Eric Blake wrote on Mon, Nov 16, 2009 at 07:57:34PM CET:
> Many
> gnulib macros are one-shot, in that they take no arguments, perform a single
> idempotent check
that does not rely on when in the configure script the check is
performed, so it could just as well be performed at most any point
e
Jim Meyering meyering.net> writes:
> > The other fix is to use AC_DEFUN_ONCE in chown.m4, rather than tweaking
> > configure.ac sections of modules files.
>
> Ah ha!
> I knew there'd be a better way to solve that.
> I've gone ahead and used AC_DEFUN_ONCE for both.
> Is there any reason to use AC
Eric Blake wrote:
> Jim Meyering meyering.net> writes:
>
>> Hoping to use the latest gnulib in coreutils, I sync'd, committed (without
>> pushing yet, of course), and tried to bootstrap. Running autoconf
>> produced warnings like this:
>>
>> configure.ac:45: warning: AC_REQUIRE: `gl_FUNC_CHOWN' w
Jim Meyering meyering.net> writes:
> Hoping to use the latest gnulib in coreutils, I sync'd, committed (without
> pushing yet, of course), and tried to bootstrap. Running autoconf
> produced warnings like this:
>
> configure.ac:45: warning: AC_REQUIRE: `gl_FUNC_CHOWN' was expanded before it
wa
ow I ended up fixing things in gnulib:
>From 1b712ba8bb1359974aa495a1a95b2185ed68e87e Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Mon, 16 Nov 2009 10:22:53 +0100
Subject: [PATCH] avoid new AC_REQUIRE expanded-before-required warnings
* modules/chown (configure.ac): Require gl_FUNC_CH
