> > >> checking for struct sockaddr_storage... no
> >
> > > Hrm.... on 5.1-CURRENT (~3 days old) it works:
> >
> > When did you last update from our CVS? I corrected the configure test
> > a couple hours ago ...
>
> Oh.... err, umm.... 'bout 10minutes ago I Sup'ed and checked.
>
> *wanders off to go read -committers*
I must have caught pgsql at a bad time last time when I was getting 5
failed checks on pgsql in the regression tests.. though I'm still
getting a failure for float8:
*** ./expected/float8-small-is-zero.out Tue Mar 11 13:01:33 2003
--- ./results/float8.out Thu Jun 12 11:34:21 2003
***************
*** 274,280 ****
--- 274,282 ---- INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400'); ERROR: Input '-10e400' is out of range for float8
INSERTINTO FLOAT8_TBL(f1) VALUES ('10e-400');
+ ERROR: Input '10e-400' is out of range for float8 INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400');
+ ERROR: Input '-10e-400' is out of range for float8 -- maintain external table consistency across platforms -- delete
allvalues and reinsert well-behaved ones DELETE FROM FLOAT8_TBL;
======================================================================
I don't know where that conversation left off, but it'd be nice to get
some kind of conditional regarding that. FreeBSD 4.X has older
floating point routines and 5.X has the latest and greatest version of
gdtoa, which fixes many standardization bits in FreeBSD's floating
point routines.
Tom, you said you needed a shell way of detecting this, does the
following work?
if [ "`uname`" = FreeBSD ]; then if [ "`sysctl -n kern.osreldate`" -ge "500110" ]; then echo "Has
newgdtoa: new float handling" else echo "Older float routines" fi
fi
-sc
--
Sean Chittenden