Just for completeness' sake:
> > I'm using -w2 which turns all warnings into serious errors
> > requiring some treatment (just like gcc -Werror does).
> But this is something we cannot support. [...]
I am perfectly happy with that position. The -w2 treatment is my
personal entertainment. I'd o
> > # if > 32 || <=== flagged error here
> This is valid ANSI C and ISO C 99 code. When you don't pass "-w2" to your
> compiler, does it show an error or a warning about this?
Omitting -w2 doesn't change anything. (Not surprisingly, since -w2 doesn't
soften
> Does your system protect against duplication of
> types out of ?
No. Neither that nor in the other direction. The conflicting
(or rather: duplicated) typedefs are also not under control of
any conditional such as __STDC__ or whatever.
Both headers have the usual #ifndef brackets protecting
> The lib/stdint.h which is generated on an IRIX 5.3 system should have
> all of the stuff you need without any change needed to md5.c or md5.h.
>
> If you want to checkout a copy of the vanilla CVS sources and do a quick
> configure and build to let us know of any warnings or errors you see,
> th
I'm not sure whether I should really chime in.
I'm mostly sending this stuff just because "What required for SGIs?"
w.r.t. stdint/inttypes has become a current topic and this fits in.
The recent gnulib stdint_.h changes for SGIs look promising to me.
However, it'll take some days for me to check t
