oops, forgot one part of the patch...remove 'false' setting to ELF_SYS...

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.

 documentation for v6.4.
Bigger updates to the installation instructions (install and config).

 in a year an a half. Much of the info was wrong and is covered more
 correctly elsewhere.

 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).

Has three pages of goofy layout at the end. Can't figure out what Applix
doesn't like about it, so giving up for now.

Okay, this shoudl provide a fix for the freebsd problem...

Added a ELF_SYS variable and check to configure.in...

Add tests for comparison operators.

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.

testing for null-pointer return code...

specific version of this result, now that tintervals actually sort
correctly.  We can always add it back if NetBSD really is different.

now that bugs in pg_operator that caused wrongly sorted results have
been corrected (I hope ... it works here, anyway).

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.

mistakes in creating pg_operator table.

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...

Fix spelling of "DIRSEPARATOR".

which one it is, and how to correct this ?

lseg_eq -> lseq_neq

Guido Weber

Updated "expected" regression output for Solaris-Sparc

 to allow ODBC library to be linked.