Skip site navigation (1) Skip section navigation (2)

Re: Various bugs with PG7.1 8th March snapshot on Solaris 8 INTEL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Justin Clift <jclift(at)iprimus(dot)com(dot)au>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Various bugs with PG7.1 8th March snapshot on Solaris 8 INTEL
Date: 2001-03-13 20:27:53
Message-ID: 22454.984515273@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> Interesting theory, but if LIBS is broken then wouldn't the backend fail
>> to run at all?  How'd they manage to pass the other regress tests?

> Presumably the backend would print an error message along the lines of
> "cannot find shared library libxyz.so" and the user would take appropriate
> configuration steps.  However, this doesn't really help when running
> configure because no user actually reads every 'checking...' line and
> tries to challenge the result by examining config.log.

Oh, I see: you posit that the user fixed the shlib configuration problem
after discovering the backend wouldn't run, but did not then go back and
re-run configure.  Yes, that makes sense.  Justin, are the INT64 flags
in your config.h wrong?

> Yet another reason to avoid AC_TRY_RUN.

The tests that we have to see whether 64-bit arithmetic actually works
are probably just unnecessary paranoia.  However, the tests to see
whether snprintf does the right thing, and with what format flags,
still seem necessary; and I see no way to handle those without a runtime
check.

Maybe the AC_TRY_RUN tests could be moved up to before we start probing
for libraries?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2001-03-13 20:31:10
Subject: Re: Various bugs with PG7.1 8th March snapshot on Solaris 8 INTEL
Previous:From: Tom LaneDate: 2001-03-13 20:00:00
Subject: Re: Various bugs with PG7.1 8th March snapshot on Solaris 8 INTEL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group