This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC headers and DJGPP port
- To: law at cygnus dot com
- Subject: Re: GCC headers and DJGPP port
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Mon, 24 Jul 2000 01:48:43 -0400 (EDT)
- CC: mrs at windriver dot com, zack at wolery dot cumb dot org, djgpp-workers at delorie dot com, gcc at gcc dot gnu dot org, martin at loewis dot home dot cs dot tu-berlin dot de
- References: <12279.964366753@upchuck>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> > > From: Mike Stump <mrs@windriver.com>
> > > Date: Sat, 22 Jul 2000 17:23:25 -0700 (PDT)
> > >
> > > > A similar argument can be made for assert.h, stddef.h, and possibly
> > > > float.h, but these headers do not cause nearly as much trouble as
> > > > limits.h. Limits.h must die.
> >
> > Such a change doesn't have to affect all platforms, and doesn't need
> > to happen in one go. It could be conditioned on some sommand-line
> > option to `configure', or be the default on only some platforms, at
> > least initially.
> No, that's a hack, plain and simple.
I believe it's no more hackyish than --disable-nls or --without-x.