Please try 7.4RC2. We have that fixed there.
----------------------------------------------------------------------- ----
Barry C.Hawkins wrote:List, Hello. I am trying to get PostgreSQL 7.3.4 installed after moving to Mac OS 10.3, known as Panther. I am using the following configure statement:
pbg417:/usr/local/src/postgresql-7.3.4 barryh$ ./configure --prefix=/usr/local/pgsql --enable-locale --enable-multibyte=UNICODE --with-openssl=/usr --with-perl --with-java --enable-syslog --with-includes=/sw/include --with-libraries=/sw/lib
Configure succeeds, but make fails with the following error:
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 tried disabling OpenSSL since I had 3 warning messages regarding OpenSSL during the configure process, but make still produces the same results. I had 7.3.4 installed on Mac OS 10.2.8 without issue. Any advice? Thanks in advance.
Regards, -- Barry C. Hawkins All Things Computed site: www.allthingscomputed.com weblog: www.allthingscomputed.com/blog/
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Bruce,
Thank you; that worked wonderfully. It configured, compiled, and installed without issue.
Regards, -- Barry C. Hawkins All Things Computed site: www.allthingscomputed.com weblog: www.allthingscomputed.com/blog/
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match