Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Jeffrey Walton
On Wed, Jul 17, 2019 at 9:41 PM Jeffrey Walton wrote: > > On Wed, Jul 17, 2019 at 9:19 PM Paul Eggert wrote: > > > > Jeffrey Walton wrote: > > > It looks like the glibc macro is a little simpler and lacks the > > > attributes: > > > > Thanks. Can you give the preprocessor output for a declaratio

Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Jeffrey Walton
On Wed, Jul 17, 2019 at 9:19 PM Paul Eggert wrote: > > Jeffrey Walton wrote: > > It looks like the glibc macro is a little simpler and lacks the attributes: > > Thanks. Can you give the preprocessor output for a declaration that fails with > Gnulib? __attribute__ ((nothrow)) seems to be causing t

Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Paul Eggert
Jeffrey Walton wrote: It looks like the glibc macro is a little simpler and lacks the attributes: Thanks. Can you give the preprocessor output for a declaration that fails with Gnulib?

Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Jeffrey Walton
On Wed, Jul 17, 2019 at 9:03 PM Paul Eggert wrote: > > Jeffrey Walton wrote: > > This fixes the issue for GCC 3.1 (Fedora 1) and GCC 3.3 (Ubuntu 4). > > I don't see how that patch could fix the issue for GCC 3.1, since it simply > changes a test to check for GCC 3.4 instead of 3.3, so GCC 3.1 shou

Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Paul Eggert
Jeffrey Walton wrote: This fixes the issue for GCC 3.1 (Fedora 1) and GCC 3.3 (Ubuntu 4). I don't see how that patch could fix the issue for GCC 3.1, since it simply changes a test to check for GCC 3.4 instead of 3.3, so GCC 3.1 should behave the same regardless of whether the patch is instal

Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Jeffrey Walton
On Wed, Jul 17, 2019 at 7:42 PM Bruno Haible wrote: > > Jeffrey Walton wrote: > > We claim to support GCC 2.95 and above. > > That's a tough claim, and you can't count on gnulib to help you on that > claim. Ack, thanks. > This means, by using gnulib you can certainly get some problems from 2005

Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Bruno Haible
Hi, Jeffrey Walton wrote: > We claim to support GCC 2.95 and above. That's a tough claim, and you can't count on gnulib to help you on that claim. It's tough, because in my experience GCC 2.95 and 2.95.1 were buggy even at that time. GCC 2.95.2 was nearly OK. GCC 2.95.3 was really OK then. But n

Re: ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Jeffrey Walton
On Wed, Jul 17, 2019 at 6:49 PM Jeffrey Walton wrote: > > I'm trying to build cURL, Git, Wget and several other utilities on > some ancient systems. We still use early Fedora and early Ubuntu VM's > to regression test. We claim to support GCC 2.95 and above. We test on > early Fedora and early Ubu

ctype.h:192: error: parse error before '{' token

2019-07-17 Thread Jeffrey Walton
Hi Everyone, I'm trying to build cURL, Git, Wget and several other utilities on some ancient systems. We still use early Fedora and early Ubuntu VM's to regression test. We claim to support GCC 2.95 and above. We test on early Fedora and early Ubuntu to verify the claim. I'm catching a lot of bui

Re: diacrit: mark deprecated

2019-07-17 Thread Bruno Haible
Bernhard Voelker wrote: > In GNU coreutils, we now get this warning during bootstrap: > > Notice from module diacrit: > This module is deprecated. Use the module > 'uninorm/canonical-decomposition' instead. > > And indeed, the 'diacrit' module is still in use by 1 source: > > $ GIT_PAGE

Re: diacrit: mark deprecated

2019-07-17 Thread Bernhard Voelker
[adding coreutils: discussion at https://lists.gnu.org/r/bug-gnulib/2019-01/msg00116.html ] On 1/21/19 6:01 AM, Jim Meyering wrote: > On Sun, Jan 20, 2019 at 5:11 PM Bruno Haible wrote: >> Hi Jim, >> >> You are listed as the maintainer of the 'diacrit' module. It doubt anyone is >> still using t