On Sat, Jun 15, 2002 at 12:38:04AM +0100, Nix wrote:
> However, that's not the problem here. line 295 in glibc-2.2.5's stdio.h
> reads:
> 
> /* Maximum chars of output to write in MAXLEN.  */
> extern int snprintf (char *__restrict __s, size_t __maxlen,
> 		     __const char *__restrict __format, ...)
>      __THROW __attribute__ ((__format__ (__printf__, 3, 4)));
> 
> where __THROW expands to throw() in C++ and nothing in C.
> 
> The fix is to take out -fno-exceptions, I think: g++ won't let
> exception-specifications past under -fno-exceptions. (Yes, this means
> -fno-exceptions in C++ on GNU/Linux and GNU/Hurd boxes is pretty
> useless.)

Problem, we actually need -fno-exceptions, because the exception
handling stuff that g++ adds conflicts with LWP, our userspace
threading code.

Jan