--enable-debug adds -g (unconditionally)
--disable-debug removes -g (if it was already in there somehow)
(giving neither does nothing)

Since none of the templates default CFLAGS with a -g you're not likely
to
end up with two -g flags. Not that they'd hurt though.

It doesn't do anything about C++.

Peter Eisentraut

works if finite() is a function.  Patch from Christof Petig.

Make sure both SRCH_INC and SRCH_LIB are checked for existances and added to
the CPPFLAGS/LDFLAGS variables...

use Autoconf-approved method of testing for predefined symbols, and move
it down to where we know what compiler to run and how to run it.

configure.in to determine if a system is ELF or not.  Note that some
of the tests earlier may be redundant but I took the safest route.

D'Arcy J.M. Cain

after checking for presence of C++ compiler.  Odd we hadn't seen any
reports of problems before...

when used with egcs --- now it does.

Give BEOS a chance ...

Apply freebsd specific patches dealign with ELF system from FreeBSD's
ports collection ...

in pl/plpgsql/src/mklang.sql.

and related files.  Also remove float.c's gratuitous redeclaration of
isinf() ... looks like there are more decls in there that ought to be
in config.h, but I'll leave well enough alone for now ...

it with configure-script tests to see whether const, inline, volatile, etc
work or not.  (Curiously, configure was already doing the work to see if
const and inline were OK, but the results were not getting plugged into
config.h :-(.)

configure, instead of having a bunch of crufty platform-specific guesses.

in
different directories.  The patch gave the option of specifying a dir
for
the tk script and if they were both in the same directory then it didn't
mind being empty.  It's small so I'm including it.  It was tested with
autoconf 2.12.

Vince.

define INT64_FORMAT in all cases.

NetBSD/macppc
LinuxPPC
FreeBSD 2.2.6-RELEASE

All of them seem happy with the regression test. Note that, however,
compiling with optimization enabled on NetBSD/macppc causes an initdb
failure (other two platforms are ok). After checking the asm code, we
are suspecting that might be a compiler(egcs) bug.

Tatsuo Ishii

Have configure check for use of %lld for int64, and if that fails, check for
use of %qd...a more generic solution then having #ifdef __<INSERT OS HERE>__
in the code...

is less likely to fail for lack of semaphores.

of MAXBACKENDS is now 1024, since all it's costing is about 32 bytes of memory
per array slot.  configure's --with-maxbackends switch now controls DEF_MAXBACKENDS
which is simply the default value of the postmaster's -N switch.  Thus,
the out-of-the-box configuration will still limit you to 64 backends,
but you can go up to 1024 backends simply by restarting the postmaster with
a different -N switch --- no rebuild required.