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

2019-07-17 Thread Jeffrey Walton
ts in hundreds of these (encountered when building gettext): In file included from regex_internal.h:24, from regex.c:68: /usr/include/ctype.h:192: error: parse error before '{' token /usr/include/ctype.h:198: error: parse error before '{' token In file inclu

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

2019-07-17 Thread Jeffrey Walton
define __NTHNL(fct) fct throw () > # else > # define __THROW > # define __THROWNL > # define __NTH(fct) fct > # define __NTHNL(fct) fct > # endif > # endif > > The strategy results in hundreds of these (encountered when building gettext): > > In file include

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 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 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 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: 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: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 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-19 Thread Paul Eggert
Jeffrey Walton wrote: This is interesting. The GCC man pages for 3.3.1 (and onwards) says nothrow is a supported attribute: https://gcc.gnu.org/onlinedocs/gcc-3.3.1/gcc/Function-Attributes.html It looks like a copy/paste error. Sorry, what's "it"? That is, are you saying that the documentation