Marc G. Fournier [Sat, 31 Oct 1998 03:58:55 +0000 (03:58 +0000)]
Minor FreeBSD fixes put in place
From: SHIOZAKI Takehiko <takehi-s@ascii.co.jp>
I tried snapshot(Oct30) and made some patches.
# I think that it is confused to manage both Makefile.shlib and
# makefiles/Makefile.*, don't you?
* configure
Now FreeBSD 2.X is not supported..., so I added its entry.
If ELF_SYSTEM is set, gmake treat it defined even though
it is "false". So nothing should be set to use "ifdef".
BSD_SHLIB etc. may have same problems.
* Makefile.shlib
As you said, FreeBSD entry is much like BSD's.
I only added ELF_SYSTEM code.
* makefiles/Makefile.freebsd
Ifdef/else/endif can not be indented with TABs.
Minor editing and markup changes as a result of preparing the Postscript
documentation for v6.4.
Bigger updates to the installation instructions (install and config).
Remove obsolete file listing support resources which has not been updated
in a year an a half. Much of the info was wrong and is covered more
correctly elsewhere.
Minor fix for Jan to remove claim in SPI and trigger chapters that
Postgres is missing a procedural language. He correctly points out
that we now have two (thanks to him, but he modestly didn't mention
that).
Tom Lane [Thu, 29 Oct 1998 17:57:52 +0000 (17:57 +0000)]
Run AC_PROG_GCC_TRADITIONAL only when running AC_PROG_CC,
ie, not when user specifies --with-CC. This corrects a scripting error
that I'm surprised hasn't been reported more often. Moving the macro call
to the earlier point in the script is correct anyway: if -traditional is needed,
it should get added to CFLAGS before we start using the compiler for
other tests.
Tom Lane [Thu, 29 Oct 1998 04:32:57 +0000 (04:32 +0000)]
I suspect that there is no longer a need for a platform-
specific version of this result, now that tintervals actually sort
correctly. We can always add it back if NetBSD really is different.
Tom Lane [Thu, 29 Oct 1998 04:29:12 +0000 (04:29 +0000)]
Update tinterval test to have correctly sorted results,
now that bugs in pg_operator that caused wrongly sorted results have
been corrected (I hope ... it works here, anyway).
Tom Lane [Thu, 29 Oct 1998 04:27:11 +0000 (04:27 +0000)]
Add new regression test to catch some simple kinds of
mistakes in creating pg_operator table. NOTE: right now, this will
fail because of conflicting definitions for point @ path operator.
I trust we're gonna fix that.
Tom Lane [Thu, 29 Oct 1998 04:22:52 +0000 (04:22 +0000)]
Fix a veritable boatload of errors in oprcom, oprnegate,
oprlsortop and oprrsortop links. There's still a bug involving
conflicting definitions for point @ path, but I'm not taking
responsibility for deciding which one is right...
Incorporate changes suggested by Tom Lane.
Update storage space estimates.
Continue cleanup.
Still need to consolidate configure parameters with new config.sgml info.
Tom Lane [Mon, 26 Oct 1998 01:03:24 +0000 (01:03 +0000)]
Fix some actual bugs exposed by compiler warnings.
(Someone forgot whether their subroutine signaled errors by a NULL pointer
return value, or a negative integer... I'm surprised gcc -Wall doesn't
catch this...)
Tom Lane [Mon, 26 Oct 1998 01:00:13 +0000 (01:00 +0000)]
Get rid of some minor compiler warnings.
(HP's cc doesn't like if you forward-declare a routine static,
and then don't make it static in the actual definition...)
Tom Lane [Mon, 26 Oct 1998 00:56:16 +0000 (00:56 +0000)]
Fix cpp-from-stdin detection so that it works even if the
compiler silently accepts an empty command line.
Don't bother searching for bison and yacc unless we are going to use them.
Add massive new docs from Peter Mount.
Includes markup for the introductory portions suitable for the User's Guide
but just put the class reference material inside a huge <programlisting>
block. Figure out what to do later...
Tom Lane [Sat, 24 Oct 1998 22:21:12 +0000 (22:21 +0000)]
Update README to reflect the fact that you don't have to
run the regression tests with a special postmaster TZ setting anymore.
Correct a few typos too.
Tom Lane [Sat, 24 Oct 1998 22:05:01 +0000 (22:05 +0000)]
Update instructions for running configure (the old ones
seem to date from some pre-autoconf interactive configure script).
Revise sequence of instructions to allow you to start the regular
postmaster run before running regression tests; there's no need to
start and kill a special postmaster for regression tests.
Update the description of interpreting regression test results.