hash.c compilation error

2006-02-17 Thread Davide Angelocola
Hi, hash.c with USE_OBSTACK fails to compile with gcc 3.3.4: hash.c:38:16: #if with no expression hash.c:78:16: #if with no expression hash.c:590:16: #if with no expression hash.c:669:16: #if with no expression hash.c:716:16: #if with no expression hash.c:832:16: #if with no expression hash.c:89

Re: canon-host problems in cygwin

2006-02-17 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 2/15/2006 4:28 PM: > And here is a patch. The cygwin list confirmed that > and are intentionally incompatible, and that > although the later is available for use in mingw compiles, it > purposefully errors out if was alre

Re: rules, rules, and more (code policy) rules

2006-02-17 Thread Jim Meyering
Simon Josefsson <[EMAIL PROTECTED]> wrote: >>> Ok. >>> How about maint.mk and maint-cfg.mk? >> >> Sounds good. Installed. > > Auto-completing maint* is causing me problem already... while this is > very minor, it also occurred to me that "cfg" is rather incorrect. > maint-cfg.mk will likely conta

Re: warning in AC_CHECK_DECL

2006-02-17 Thread Paul Eggert
Eric Blake <[EMAIL PROTECTED]> writes: > With my proposed patch to AC_FUNC_STRERROR_R, gnulib's m4/strerror_r.m4 is > now out of date. Either we need to update the various gnulib macros > borrowed from CVS autoconf to override bugs in autoconf 2.59, or we need > to release autoconf 2.60. We shou

Re: warning in AC_CHECK_DECL

2006-02-17 Thread Jim Meyering
Eric Blake <[EMAIL PROTECTED]> wrote: >> Followup - with the earlier patch fixed, now AC_FUNC_STRERROR_R has a >> warning, that was making the -Wall -Werror compilation think that >> strerror_r returned int instead of char* on cygwin. >> >> 2006-02-16 Eric Blake <[EMAIL PROTECTED]> >> >> * l