-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 3/27/2009 1:13 AM:
>> Nope. Cygwin doesn't use glibc, so 'info libc' fails to turn up anything
>> at all. Do you have a preferred way to skip this test on non-Linux
>> platforms, since glibc's info manual is unlikely to a
Eric Blake wrote:
> According to Jim Meyering on 3/26/2009 7:32 AM:
>>> failing on sc_strftime_check, with "info: No menu item `date' in node
>>> `(libc.info.gz)Top'").
>>
>> For me, that rule's "info libc date calendar format" command
>> prints the "21.4.5 Formatting Calendar Time" section.
>> Not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 3/26/2009 7:32 AM:
>> failing on sc_strftime_check, with "info: No menu item `date' in node
>> `(libc.info.gz)Top'").
>
> For me, that rule's "info libc date calendar format" command
> prints the "21.4.5 Formatting Calenda
Eric Blake wrote:
> My next 'make syntax-check' failure comes from sc_tight_scope. On cygwin,
> all exported symbols include a leading underscore, so the check complains
> about a large number of these:
Thanks for testing!
> The attached patch relaxes that rule in sr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My next 'make syntax-check' failure comes from sc_tight_scope. On cygwin,
all exported symbols include a leading underscore, so the check complains
about a large number of these:
_main
_usage
along with several other false positives, f
