bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gl_* check do nothing?


From: Sam Steingold
Subject: Re: gl_* check do nothing?
Date: Wed, 29 Sep 2010 14:09:04 -0400

On Wed, Sep 29, 2010 at 11:50 AM, Eric Blake <address@hidden> wrote:
> On 09/29/2010 09:34 AM, Sam Steingold wrote:
>>
>> this part of my configure.in:
>
> You haven't switched to configure.ac yet?

http://www.cygwin.com/acronyms/#PTC :-)

>> AC_FUNC_CHOWN
>> gl_FUNC_MKTIME
>> gl_FUNC_GNU_STRFTIME
>> gl_FUNC_STRPTIME
>> gl_TIME_MODULE_INDICATOR([strptime])
>> gl_GETDATE
>> gl_FUNC_STRVERSCMP
>> gl_STRING_MODULE_INDICATOR([strverscmp])
>> gl_FUNC_UNAME
>> gl_SYS_UTSNAME_MODULE_INDICATOR([uname])
>> gl_FUNC_STRERROR
>> gl_STRING_MODULE_INDICATOR([strerror])
>
> Why are you calling these macros directly?  It's much easier to call a
> single gl_INIT (after gl_INIT_EARLY) to get it all taken care of for you.

because I did not know that gl_INIT called them.
thanks for pointing this out.

>> how do I get the full list of all functions which gnulib actually
>> replaced in the current build?
>
> For all gnulib replacements that follow modern paradigms, the fastest way to
> see what needed replacement is 'grep REPLACE_.\*1 config.log',

no matches.
great!

> although that
> may miss out on a few of the older-style function replacements (for example,
> poll didn't show up in that paradigm until just this week).

are there many of those?

-- 
Sam Steingold <http://sds.podval.org>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]