> Boo. And if we change libdecnumber to use gnulib's version we'll > undoubtedly break gcc. If we provide gstdint.h in the gdb directory > which redirects to <stdint.h>, will libdecnumber pick it up at this > point?
That's pretty ingenious. Indeed, that works, since the include order when compiling GDB files is the gdb directory, ahead of all other dependencies. I'll send a patch shortly after having tested it. > > #if ! defined __cplusplus || defined __STDC_CONSTANT_MACROS > > > > /* Get WCHAR_MIN, WCHAR_MAX. */ > > # if ! (defined WCHAR_MIN && defined WCHAR_MAX) > > # include <wchar.h> > > # endif > > > > #endif > > > > Perhaps we could somehow generate the macro definitions ourselves, > > which would help avoiding the include. Ideally, gnulib would take > > care of that and avoid the include, or we could compute the WCHAR_MIN > > and WCHAR_MAX during the GDB configury and define the macros just > > before including gnulib/stdint.h. > > I agree that having gnulib pull in wchar.h is very unfortunate. The > gnulib folks, CC'd, are very responsive - maybe someone on bug-gnulib > has an idea on how to fix this? That would be nice :-). I wanted to have a look, but m4/stdint.m4 needs a little bit of study time before I can understand it all... -- Joel
