[torquedev] Re: trunk not compiiing on OS X 10.4

[Glen Beane]

On 8/29/07, Garrick Staples <garrick at usc.edu> wrote:
> On Wed, Aug 29, 2007 at 02:02:09PM -0400, Glen Beane alleged:
> > On 8/29/07, Garrick Staples <garrick at usc.edu> wrote:
> > > On Wed, Aug 29, 2007 at 05:53:45PM +0200, Matti Bickel alleged:
> > > > Glen Beane <glen.beane at gmail.com> wrote:
> > > > > int main (int argc, char **argv)
> > > > > {
> > > > >    double x = 1e500;
> > > > >
> > > > >    return 0;
> > > > > }
> > > >
> > > > Here's what the C99 Standard says (5.2.4.2.2):
> > > > The values given in the following list shall be replaced by constant
> > > > expressions with implementation-defined values that are greater than or
> > > > equal to those shown:
> > > > - maximum representable finite floating-point number
> > > > FLT_MAX  1E+37
> > > > DBL_MAX  1E+37
> > > > LDBL_MAX 1E+37
> > >
> > > I don't see any mention of HUGE_VAL in that section.  The first relavent
> > > section seems to be 7.12.2.1.
> > >
> > > >
> > > > You can't *expect* an arch to support 1e500, afaik. Haven't had a look
> > > > at Apple's gcc in a while, here are my values:
> > >
> > > We don't care about 1e500, that's apple gcc's value for HUGE_VAL; which we do
> > > expect to be supported.
> > >
> >
> >
> > The gcc 4.0 installed on my mac has a timestamp from May 2006,  and I
> > have definately built torque since then.  When was -pedantic added to
> > the default CFLAGS?  It looks lke I haven't done much torque work on
> > this laptop since April.  I suspect this may have been a problem for a
> > while
>
> Oh, I dunno.  Some time earlier this year.  It is only default when using gcc.
> Just use --disable-gcc-warnings.

that works,   and now I don't have to worry about implicitly declaring
bindresvport either

I'm sure these warnings have alwasy been around on OS X, but what you
don't know doesn't hurt you I guess :P  - I'll just keep ignoring them
for now (and maybe file a bug report with Apple)