Re: [bug-gnulib] Re: on IRIX-5.3 & SGI-cc

2006-06-27 Thread Larry Jones
Mark D. Baushke writes: > > It would be good to understand how to fix the IRIX 5.x without breaking > the IRIX 6.x compilation. It appears that the testing of the last run > on an SGI box failed during the sshstdio-6 test. Yep -- maybe more cleanup is needed in the test? --- wrapper.dif Mon Jun

Re: [bug-gnulib] Re: on IRIX-5.3 & SGI-cc

2006-06-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Martin, I have Installed Bruno's latest GNULIB changes into the CVS sources. If there are still problems, it would be good to know what you are seeing out of the 'configure' command... both the output and selected parts of the config.log file.

Re: [bug-gnulib] Re: on IRIX-5.3 & SGI-cc

2006-06-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Martin, As an FYI, one of the test machines that builds the CVS sources nightly is an SGI IRIX64 running 6.5 (Hmmm... I had thought we also had an SGI IRIX 5.3 out there somewhere, but I must have been confused as I do not see any results from such

Re: [bug-gnulib] Re: on IRIX-5.3 & SGI-cc

2006-06-27 Thread Bruno Haible
Martin Neitzel wrote: > > > # 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. OK, thanks, I'

Re: [bug-gnulib] on IRIX-5.3 & SGI-cc

2006-06-27 Thread Martin Neitzel
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

Re: [bug-gnulib] Re: on IRIX-5.3 & SGI-cc

2006-06-27 Thread Martin Neitzel
> > # 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

Re: [bug-gnulib] Re: on IRIX-5.3 & SGI-cc

2006-06-26 Thread Bruno Haible
Mark D. Baushke wrote: > * stdint_.h (__bsdos__): BSD/OS 4.2 needs to include >to avoid a generated that redifines > typedefs already found in . Thanks, I'm putting this into gnulib. > #if @HAVE_STDINT_H@ >/* Other systems may have an incomplete . */ > -# includ

Re: [bug-gnulib] Re: on IRIX-5.3 & SGI-cc

2006-06-26 Thread Bruno Haible
Martin Neitzel wrote: > into this illegal stdint.h code: > > /* wint_t limits */ > #ifndef WINT_MIN > # if 0 > # if > 32 ||<=== flagged error here > # define WINT_MIN (-1L << ( - 1)) (<=== silently borked) > # else This is valid ANSI C and IS

Re: [bug-gnulib] on IRIX-5.3 & SGI-cc

2006-06-26 Thread Bruno Haible
Martin Neitzel wrote: > This is CVS on a SGI Indigo (R3000, 32bit) running IRIX-5.3 and SGI's > commercial "IRIX Developer Option" cc (ANSI C as in ISO :1990 or > c89). OK, we can support this platform. > I'm using -w2 which turns all warnings into serious errors > requiring some treatment (just

Re: on IRIX-5.3 & SGI-cc

2006-06-23 Thread Martin Neitzel
> 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

Re: on IRIX-5.3 & SGI-cc

2006-06-23 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Marti, I have committed a change to CVS top-of-tree that may help you. Does your system protect against duplication of types out of ? -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEnD0ZCg7APGsDnFERAjXSAJ9

Re: on IRIX-5.3 & SGI-cc

2006-06-23 Thread Martin Neitzel
> 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

on IRIX-5.3 & SGI-cc

2006-06-23 Thread Martin Neitzel
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

Re: on IRIX-5.3 & SGI-cc

2006-06-23 Thread Paul Eggert
This is making me more and more inclined to switch to a stdint.h replacement, not something that tries to augment existing broken systems. It would be much simpler to maintain, I think. I'll work on a proposal and try to have something ready in a day or two.

Re: on IRIX-5.3 & SGI-cc

2006-06-23 Thread Mark D. Baushke
Hi Martin, The CVS project has forked from the GNULIB project slightly for the stdint stuff as I have not seen any commit to gnulib to support the SGI compilation problems we had observed. I have hopes that they will either adopt our changes or equivalent changes so that we can once more use their