![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I see test failures in float4, float8 and misc. |
#3
| |||
| |||
|
|
I see test failures in float4, float8 and misc. What configure options did you use? What compiler are you using? Did you specify any custom compiler or linker options? |
|
I've built PostgreSQL 8.0.0 (from CVS) on Solaris 9/sparc many times with gcc 3.4.2 and all "make check" tests pass. |
#4
| |||
| |||
|
|
The configure command was: $ ./configure --prefix=/usr/local/pgsql-8.0.0 --enable-thread-safety --with-includes=/export/home/vincze/include --with-libs=/export/home/vincze/lib The readline library is installed under my home, that's why the --with-includes/libs are there. |
|
I have gcc 2.96 and haven't specified any custom options to it or to the linker. |
|
I've built PostgreSQL 8.0.0 (from CVS) on Solaris 9/sparc many times with gcc 3.4.2 and all "make check" tests pass. I've compiled from the final tarball - maybe something's changed since you got the sources from CVS? |
#5
| |||
| |||
|
|
On Thu, Jan 27, 2005 at 02:08:36PM -0500, Tamas Vincze wrote: I've compiled from the final tarball - maybe something's changed since you got the sources from CVS? I've been following the 8.0 development for months, doing CVS updates and rebuilding almost daily, include once earlier this morning. I don't remember seeing any "make check" failures recently. |
#6
| |||
| |||
|
|
When I get a chance I'll do a build with --enable-thread-safety and without --enable-debug and see if it matters. |
#7
| |||
| |||
|
|
Is anything else under there? |
|
Have you tried gcc 3.x? |
#8
| |||
| |||
|
|
A few months ago an issue with strtod() on Solaris came up: http://archives.postgresql.org/pgsql...8/msg00073.php http://archives.postgresql.org/pgsql...8/msg00127.php I wonder if you're experiencing a related or similar problem that only shows up with certain build tools. |
#9
| |||
| |||
|
|
But I guess my only option now is to upgrade my build tools and give it another try... |
#10
| |||
| |||
|
|
The errors were the following: template1=# SELECT 'NaN'::float4; ERROR: 22003: type "real" value out of range: overflow LOCATION: CheckFloat4Val, float.c:219 The code around float.c:219 looks like this: if (fabs(val) > FLOAT4_MAX) ereport(ERROR, (errcode(ERRCODE_NUMERIC_VALUE_OUT_OF_RANGE), errmsg("type \"real\" value out of range: overflow"))); I wonder what a debugging printf() would show for val, fabs(val), and FLOAT4_MAX here. |
![]() |
| Thread Tools | |
| Display Modes | |
| |