Re: Hacking PostgreSQL to work in Mac OS X 10.3 (Panther 7B85) - Mailing list pgsql-hackers

After spending a few hours of trying to get Postgresql7.3.4 to build
from source (tar.gz) on a Panther (release, not beta) system, I find
that I am still having the same errors described in the original post
to this thread. It is a clean install as of yesterday, with readline
installed via fink.

# ./configure --with-includes=/sw/include/ --with-libraries=/sw/lib
--with-perl

then:

#make

yields this error at then end:

In file included from /usr/include/machine/param.h:30,                from /usr/include/sys/socket.h:67,
from../../../../src/include/libpq/pqcomm.h:28,                from ../../../../src/include/libpq/libpq-be.h:24,
      from ../../../../src/include/libpq/libpq.h:21,                from printtup.c:20:
 
/usr/include/ppc/param.h:98: macro "btodb" requires 2 arguments, but
only 1 given
/usr/include/ppc/param.h:100: macro "dbtob" requires 2 arguments, but
only 1 given
make[4]: *** [printtup.o] Error 1
make[3]: *** [common-recursive] Error 2
make[2]: *** [access-recursive] Error 2
make[1]: *** [all] Error 2
make: *** [all] Error 2


I have installed the XCode tools that came with Panther and ran
Software update to get everything up to date. Is there another
(better?) way to fix this than altering the header files as James
inidcated in his original post? there is no /opt, so I don't think it
is a lingering library there.

Kirk Gleason

jwilson@lithiumcorp.com (James Wilson) wrote in message news:<6CF21BDE-FEAA-11D7-A7CA-000A957C9590@lithiumcorp.com>...
> Nicely spotted, yeah that's what is causing these issue. The reason 
> -L/opt/local/lib is in there is due to it being ./configured with 
> --with-libraries=/opt/local/lib and --with-includes=/opt/local/include. 
> Those configure options are necessary to ensure the configure found the 
> darwinport-installed readline et.al. which are in /opt/local/lib and 
> /opt/local/include
> 
> Removing the old postgres libs would resolve this build issue, but 
> makes it a bit painful for users upgrading from an existing 
> installation.
> 
> On 15/10/2003, at 4:03 AM, Tom Lane wrote:
> 
> > James Wilson <jwilson@lithiumcorp.com> writes:
> >> make -C ecpglib all
> >> gcc -no-cpp-precomp -g -O2 -Wall -Wmissing-prototypes
> >> -Wmissing-declarations  -bundle execute.o typename.o descriptor.o
> >> data.o error.o prepare.o memory.o connect.o misc.o
> >> -L../../../../src/port -L/opt/local/lib -L../pgtypeslib -lpgtypes
> >> -L../../../../src/interfaces/libpq -lpq -lm   -o libecpg.so.4.0
> >> ld: Undefined symbols:
> >> _PQfreemem
> >> _PQresultErrorField
> >> _PQsetNoticeReceiver
> >> _last_path_separator
> >
> > I'll bet you have an old libpq in /opt/local/lib.  Why is that getting
> > included in the link anyway?
> >
> >             regards, tom lane
> >
> >
> -------------------
> James Wilson
> CCIE #6662
> 
> LithiumCorp Pty Ltd
> 
> mobile: 0422 22 3742
> email: jwilson@lithiumcorp.com
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings