With Shakespearian flourish, Darren King writes:
> > I haven't tested this with PostgreSQL itself yet, but I just compiled my
> > check-code without -lbsd and everything seems to have worked 100% fine.
> > If that works for the database, all we should need to do is rip out -lbsd.
>
> I used to take it out, but when it was moved after the -lm to find the right
> pow(), I stopped. What about fork vs vfork? If I took the -lbsd off, I had
> to fudge the config.h and undefine HAVE_VFORK. That was the only function
> from libbsd that was used.
<nod> I ripped out libbsd and HAVE_VFORK (the hard way, via configure,
to make sure it wasn't hiding anything on me), and everything compiled
cleanly. datetime failed with only 2 errors, which seem to be the known
datetime/ timespan bug Thomas patched. abstime and horology also failed,
still checking those.
> So using libbsd broke 41 for you? I'll have to double check my stuff again.
> At one time I was compiling without libbsd after undefining HAVE_VFORK, so
> maybe I got my correct results then and haven't rerun the regression tests
> since the -lm and -lbsd were switched.
Using -lbsd under 4.1 broke the test script I sent you earlier. (-lm was
not involved.) Removing libbsd and the ftime() calls made int timezone
work fine. I can't test PostgreSQL under AIX 4.1, the 4.1 box I'm using
is a college alumni account with limited space.
However, the "new" ordering (-lm -lbsd) definitely didn't fix things
for me under AIX 3.2.5. Removing -lbsd/vfork seems to have helped.
> *sigh*...more crap to track down...now I know why AIX rhymes with "aches"...
Took you this long to come to that conclusion? 8)
-Frank
- --
Frank R. Dana, Jr. Senior Associate Programmer
danaf@ans.net ANS Communications
(914) 789-5449 100 Clearbrook Rd. Elmsford, NY 10523
Pager: 800-946-4646 pin# 1420717
------------------------------
