gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -g -Wall
-Wmissing-prototypes -Wmissin g-declarations -I../../../../src/include
-c -o printtup.o printtup.c -MMD
In file included from ../../../../src/include/libpq/libpq-be.h:22,
from
It would seem the configure test isn't picking up on the structure.
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
--snip--
checking for struct sockaddr_storage... no
FreeBSD sys/socket.h is attached.
Failing configure test below
Rod Taylor [EMAIL PROTECTED] writes:
It would seem the configure test isn't picking up on the structure.
It works here (where works is defined as finds the struct on Linux
and doesn't find it on HPUX --- both correct according to a search
of /usr/include). You'll need to dig into why it fails
It would seem the configure test isn't picking up on the structure.
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
--snip--
checking for struct sockaddr_storage... no
Hrm on 5.1-CURRENT (~3 days old) it works:
checking
Sean Chittenden [EMAIL PROTECTED] writes:
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 ...
regards, tom lane
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*
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
Sean Chittenden [EMAIL PROTECTED] writes:
Tom, you said you needed a shell way of detecting this, does the
following work?
No, I need something that will work in the regression test resultmap,
which basically only knows about the platform identifier string
computed by config.guess.
We could
Tom, you said you needed a shell way of detecting this, does the
following work?
No, I need something that will work in the regression test
resultmap, which basically only knows about the platform identifier
string computed by config.guess.
We could change
We could change
float8/i.86-.*-freebsd=float8-small-is-zero
to
float8/i.86-.*-freebsd4=float8-small-is-zero
This change compiles / regresses fine for me, but I didn't read the
whole thread to try to see what to look for.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key:
We could change
float8/i.86-.*-freebsd=float8-small-is-zero
to
float8/i.86-.*-freebsd4=float8-small-is-zero
This change compiles / regresses fine for me, but I didn't read the
whole thread to try to see what to look for.
FreeBSD 5.1 imported gdtoa which fixed the handling of
Rod Taylor [EMAIL PROTECTED] writes:
We could change
float8/i.86-.*-freebsd=3Dfloat8-small-is-zero
to
float8/i.86-.*-freebsd4=3Dfloat8-small-is-zero
This change compiles / regresses fine for me, but I didn't read the
whole thread to try to see what to look for.
Good enough --- change
We could change
float8/i.86-.*-freebsd=3Dfloat8-small-is-zero
to
float8/i.86-.*-freebsd4=3Dfloat8-small-is-zero
This change compiles / regresses fine for me, but I didn't read the
whole thread to try to see what to look for.
Good enough --- change committed.
Does anyone know if
Sean Chittenden [EMAIL PROTECTED] writes:
Does anyone know if FreeBSD 3.* or before still exist in the wild?
We might have to tweak the pattern to match those too.
Ehh it probably does. I get emails once every 2-3 mo from
someone running it on a 2.x box and that code's probably 6-8
14 matches
Mail list logo
