Thread: 8.0.3 build error on Mac OS X 10.4
8.0.3 does not build for me on Mac OS X 10.4. Anyone else seeing
this error, and will it be fixed in the next release?
Thanks,
-M@
gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith -
Wendif-labels -fno-strict-aliasing -DFRONTEND -I. -I../../../src/
include -I../../../src/port -c -o thread.o thread.c
ar crs libpq.a `lorder fe-auth.o fe-connect.o fe-exec.o fe-misc.o fe-
print.o fe-lobj.o fe-protocol2.o fe-protocol3.o pqexpbuffer.o
pqsignal.o fe-secure.o md5.o ip.o wchar.o encnames.o noblock.o
pgstrcasecmp.o thread.o | tsort`
usage: join [-a fileno | -v fileno ] [-e string] [-1 field] [-2 field]
[-o list] [-t char] file1 file2
ranlib libpq.a
gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith -
Wendif-labels -fno-strict-aliasing -dynamiclib -install_name /usr/
local/pgsql/lib/libpq.4.dylib -compatibility_version 4 -
current_version 4.0 -multiply_defined suppress fe-auth.o fe-
connect.o fe-exec.o fe-misc.o fe-print.o fe-lobj.o fe-protocol2.o fe-
protocol3.o pqexpbuffer.o pqsignal.o fe-secure.o md5.o ip.o wchar.o
encnames.o noblock.o pgstrcasecmp.o thread.o -L../../../src/port -
lresolv -o libpq.4.0.dylib
/usr/bin/libtool: for architecture: cputype (16777234) cpusubtype (0)
file: -lSystem is not an object file (not allowed in a library)
make[3]: *** [libpq.4.0.dylib] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all] Error 2
make: *** [all] Error 2
On May 19, 2005, at 10:27 AM, Matthew Hixson wrote:
> 8.0.3 does not build for me on Mac OS X 10.4. Anyone else seeing
> this error, and will it be fixed in the next release?
I just built 8.0.3 on Mac OS X 10.4.1 just fine. I installed
bison-1.875 (simple ./configure, make, sudo make install) before
doing the installation. I don't know if this is part of the issue or
not. Here was my configure for the PostgreSQL installation.
./configure --prefix=${PGINSTROOT} --with-pgport=${PGPORT} --enable-
syslog --with-includes=/usr/include/ --with-libraries=/usr/lib/
The --with-includes and --with-libraries are to make sure the
configure picks up readline. It's nice that readline is installed
with Xcode now!
Hope things work out for your installation.
Michael Glaesemann
grzm myrealbox com
On May 19, 2005, at 10:48 AM, Michael Glaesemann wrote:
>
> On May 19, 2005, at 10:27 AM, Matthew Hixson wrote:
>
>
>> 8.0.3 does not build for me on Mac OS X 10.4. Anyone else seeing
>> this error, and will it be fixed in the next release?
>>
>
> I just built 8.0.3 on Mac OS X 10.4.1 just fine. I installed
> bison-1.875 (simple ./configure, make, sudo make install) before
> doing the installation. I don't know if this is part of the issue
> or not. Here was my configure for the PostgreSQL installation.
>
> ./configure --prefix=${PGINSTROOT} --with-pgport=${PGPORT} --
> enable-syslog --with-includes=/usr/include/ --with-libraries=/usr/lib/
I should add that PGINSTROOT and PGPORT are environmental variables
which I have set to /usr/local/pgsql/pgsql-8.0.3 and 54803,
respectively. (I run more than one PG installation my box.)
Michael Glaesemann
grzm myrealbox com
Michael Glaesemann <grzm@myrealbox.com> writes:
> On May 19, 2005, at 10:27 AM, Matthew Hixson wrote:
>> 8.0.3 does not build for me on Mac OS X 10.4. Anyone else seeing
>> this error, and will it be fixed in the next release?
> I just built 8.0.3 on Mac OS X 10.4.1 just fine.
IIRC this isn't the first report of build problems on 10.4, and not the
first report of success either. Somebody needs to look into exactly
what's going on. (Don't look at me, I have not bought 10.4 yet...)
regards, tom lane
On May 18, 2005, at 8:21 PM, Tom Lane wrote: > Michael Glaesemann <grzm@myrealbox.com> writes: > >> On May 19, 2005, at 10:27 AM, Matthew Hixson wrote: >> >>> 8.0.3 does not build for me on Mac OS X 10.4. Anyone else seeing >>> this error, and will it be fixed in the next release? >>> > > >> I just built 8.0.3 on Mac OS X 10.4.1 just fine. >> > > IIRC this isn't the first report of build problems on 10.4, and not > the > first report of success either. Somebody needs to look into exactly > what's going on. (Don't look at me, I have not bought 10.4 yet...) After upgrading to 10.4.1 and using Michael's parameters to ./ configure I still get the exact same build error. Any Postgres hackers out there interested in logging into my machine and seeing what they can do to fix this? -M@
On May 19, 2005, at 12:21 PM, Tom Lane wrote: > Michael Glaesemann <grzm@myrealbox.com> writes: > >> On May 19, 2005, at 10:27 AM, Matthew Hixson wrote: >> >>> 8.0.3 does not build for me on Mac OS X 10.4. Anyone else seeing >>> this error, and will it be fixed in the next release? >>> > > >> I just built 8.0.3 on Mac OS X 10.4.1 just fine. >> > > IIRC this isn't the first report of build problems on 10.4, and not > the > first report of success either. Somebody needs to look into exactly > what's going on. (Don't look at me, I have not bought 10.4 yet...) For the record, my machine is a clean install of 10.4.0 + Xcode, then upgraded to 10.4.1. I installed Bison 1.875 (as previously mentioned), but otherwise it's a stock system. No fink, no Darwinports, nothing but PostgreSQL. laughter:~ glaesema$ which gcc /usr/bin/gcc laughter:~ glaesema$ gcc -v Reading specs from /usr/lib/gcc/powerpc-apple-darwin8/4.0.0/specs Configured with: /private/var/tmp/gcc/gcc-4061.obj~8/src/configure -- disable-checking --prefix=/usr --mandir=/share/man --enable- languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^+.-]*$/ s/$/-4.0/ --with-gxx-include-dir=/include/gcc/darwin/4.0/c++ -- build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 -- target=powerpc-apple-darwin8 Thread model: posix gcc version 4.0.0 20041026 (Apple Computer, Inc. build 4061) Possibly there's a issue with upgrading from 10.3.x to 10.4? Maybe using a different gcc? I'm not very experienced reading installation messages, so I'm not really sure what error Matthew's getting. I've attached what I think is the corresponding section from my installation. I've saved the whole terminal session, so if anyone needs anything else, just let me know. Michael Glaesemann grzm myrealbox com ----- gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith - Wdeclaration-after-statement -Wold-style-definition -Wendif-labels - fno-strict-aliasing -DFRONTEND -I. -I../../../src/include -I/usr/ include/ -I../../../src/port -c -o thread.o thread.c ar crs libpq.a `lorder fe-auth.o fe-connect.o fe-exec.o fe-misc.o fe- print.o fe-lobj.o fe-protocol2.o fe-protocol3.o pqexpbuffer.o pqsignal.o fe-secure.o md5.o ip.o wchar.o encnames.o noblock.o pgstrcasecmp.o thread.o | tsort` tsort: cycle in data tsort: fe-exec.o tsort: fe-protocol2.o tsort: fe-connect.o tsort: fe-protocol3.o tsort: cycle in data tsort: fe-exec.o tsort: fe-protocol2.o tsort: cycle in data tsort: fe-exec.o tsort: fe-misc.o tsort: cycle in data tsort: fe-auth.o tsort: fe-connect.o ranlib libpq.a gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith - Wdeclaration-after-statement -Wold-style-definition -Wendif-labels - fno-strict-aliasing -dynamiclib -install_name /usr/local/pgsql/ pgsql-8.0.3/lib/libpq.4.dylib -compatibility_version 4 - current_version 4.0 -multiply_defined suppress fe-auth.o fe- connect.o fe-exec.o fe-misc.o fe-print.o fe-lobj.o fe-protocol2.o fe- protocol3.o pqexpbuffer.o pqsignal.o fe-secure.o md5.o ip.o wchar.o encnames.o noblock.o pgstrcasecmp.o thread.o -L../../../src/port -L/ usr/lib/ -lresolv -o libpq.4.0.dylib rm -f libpq.4.dylib ln -s libpq.4.0.dylib libpq.4.dylib rm -f libpq.dylib ln -s libpq.4.0.dylib libpq.dylib make -C include all make[4]: Nothing to be done for `all'.
On May 19, 2005, at 1:34 AM, Matthew Hixson wrote: > /usr/bin/libtool: for architecture: cputype (16777234) cpusubtype (0) > file: -lSystem is not an object file (not allowed in a library) > After upgrading to 10.4.1 and using Michael's parameters to > ./configure I still get the exact same build error. Any Postgres > hackers out there interested in logging into my machine and seeing > what they can do to fix this? [Wild stabs in the dark to follow] What kind of Mac is it? The error had something to do with cputype. When I installed XCode 2.0 yesterday I noticed it installs gcc 3 and 4. Maybe you could try using gcc 3 and see if it makes a difference. John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL
On May 19, 2005, at 5:42 AM, John DeSoi wrote: > > On May 19, 2005, at 1:34 AM, Matthew Hixson wrote: > >> /usr/bin/libtool: for architecture: cputype (16777234) cpusubtype >> (0) file: -lSystem is not an object file (not allowed in a library) >> > > >> After upgrading to 10.4.1 and using Michael's parameters to ./ >> configure I still get the exact same build error. Any Postgres >> hackers out there interested in logging into my machine and seeing >> what they can do to fix this? >> > > [Wild stabs in the dark to follow] > > What kind of Mac is it? The error had something to do with cputype. > > When I installed XCode 2.0 yesterday I noticed it installs gcc 3 > and 4. Maybe you could try using gcc 3 and see if it makes a > difference. My machine is a 1Ghz G4 Powerbook. This machine was upgraded from 10.3.9 to 10.4 and then brought up to 10.4.1 through software update. I have Xcode 1.1 installed and my gcc is: mhixson@Titan:~/$ gcc -v Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs Thread model: posix gcc version 3.3 20030304 (Apple Computer, Inc. build 1495) So perhaps I should just upgrade XCode and that'll fix my problem. -M@
On May 18, 2005, at 9:27 PM, Matthew Hixson wrote: > /usr/bin/libtool: for architecture: cputype (16777234) cpusubtype > (0) file: -lSystem is not an object file (not allowed in a library) I had some issues with this error on a few other things on my Tiger box. After I installed Xcode2 things worked fine. Try installing xcode2 and let us know. (And I compiled and run Tiger on my tiger machine here, with xcode2, gcc 4) -- Jeff Trout <jeff@jefftrout.com> http://www.jefftrout.com/ http://www.stuarthamm.net/
On May 19, 2005, at 9:27 AM, Jeff Trout wrote:
>
> On May 18, 2005, at 9:27 PM, Matthew Hixson wrote:
>
>
>
>> /usr/bin/libtool: for architecture: cputype (16777234) cpusubtype
>> (0) file: -lSystem is not an object file (not allowed in a library)
>>
>
> I had some issues with this error on a few other things on my Tiger
> box.
> After I installed Xcode2 things worked fine.
>
> Try installing xcode2 and let us know.
>
> (And I compiled and run Tiger on my tiger machine here, with
> xcode2, gcc 4)
I just installed Xcode 2 and postgres built successfully. A 'make
check' also says all 96 tests passed.
Thanks for the help everyone. Keep up the good work.
-M@
For what it is worth... I have 10.4.1 (Tiger) (archived and ) installed on my old 933MHZ QuickSiver. I also have Xcode 2.0 installed. When I compiled 8.0.3 it seemed to generated many more warnings with 4.0 gcc than the older 3.3 gcc. At least that is my recollection... I have installed the rascal and it appears to be working... Jerry
I also thought I saw quite a few more warnings this time than in the past. -M@ On May 19, 2005, at 11:05 AM, Jerry LeVan wrote: > For what it is worth... > > I have 10.4.1 (Tiger) (archived and ) installed on my > old 933MHZ QuickSiver. > > I also have Xcode 2.0 installed. > > When I compiled 8.0.3 it seemed to generated many more > warnings with 4.0 gcc than the older 3.3 gcc. At least > that is my recollection... > > I have installed the rascal and it appears to be working... > > Jerry > > > > ---------------------------(end of > broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings > >
hi all,
reading here, it seems builds on 'virgin' Tiger are behaving themselves ...
just fyi & fwiw, a pgsql v803 build on OSX 10.4.1 is also very nicely tolerant
of a /usr/local mod'd system, resulting in:
% otool -L /usr/local/pgsql/bin/postgres
/usr/local/pgsql/bin/postgres:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
88.0.0)
/usr/local/ssl/lib/libssl.0.9.7.dylib (compatibility version 0.9.0, current
version 0.9.7)
/usr/local/ssl/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.0, current
version 0.9.7)
/Library/Frameworks/Tcl.framework/Versions/8.5/Tcl (compatibility version
8.5.0, current version 8.5.0)
/usr/local/lib/libreadline.5.0.dylib (compatibility version 5.0.0, current
version 5.0.0)
/usr/local/lib/libintl.3.dylib (compatibility version 8.0.0, current version
8.3.0)
/usr/lib/libpam.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.2)
/usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version
365.0.0)
/usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 92.0.0)
where env:
Mac OSX 10.4.1
TclTkAquaBI-8.4.9.1.dmg
Berkeley-DB v4.3.28 w/ strong crypto
Gettext v0.14.4
% perl -V
Summary of my perl5 (revision 5 version 8 subversion 6) configuration:
Platform:
osname=darwin, osvers=8.1.0, archname=darwin-thread-multi-2level
uname='darwin devbox 8.1.0 darwin kernel version 8.1.0: tue may 10
18:16:08 pdt 2005; root:xnu-792.1.5.obj~4release_ppc power macintosh
powerpc '
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES
PERL_IMPLICIT_CONTEXT
Built under darwin
Compiled at May 18 2005 22:18:53
%gcc --version
powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 20041026 (Apple Computer, Inc.
build 4061)
% glibtool --version
ltmain.sh (GNU libtool) 1.5.18 (1.1220.2.245 2005/05/16 08:55:27)
% automake --version
automake (GNU automake) 1.9.5
% autoconf --version
autoconf (GNU Autoconf) 2.59
% openssl version
OpenSSL 0.9.7g 11 Apr 2005
and, libreadline (v5.0) is picked up from my external build:
-r-xr-xr-x 1 root staff 416616 May 18 11:12
/usr/local/lib/libreadline.5.0.dylib
lrwxr-xr-x 1 root staff 21 May 18 11:12 /usr/local/lib/libreadline.dylib
-> libreadline.5.0.dylib
rather than from Tiger's native link to libedit:
lrwxr-xr-x 1 root wheel 13 May 10 09:40 /usr/lib/libreadline.dylib ->
libedit.dylib
and building as:
cd /usr/ports/postgresql-8.0.3
ln -sf /usr/include/pam /usr/include/security
perl -pi -e 's/AC_PROG_RANLIB/AC_PROG_LIBTOOL/g'
/usr/ports/postgresql-8.0.3/configure.in
setenv CPPFLAGS "-I/usr/local/ssl/include
-I/Library/Frameworks/Tcl.framework/Headers -I/usr/local/include"
setenv LDFLAGS "-bind_at_load -ldl -L/usr/local/ssl/lib -lssl -lcrypto
-F/Library/Frameworks -framework Tcl -L/usr/local/lib -lreadline"
glibtoolize --force --copy
aclocal -I config
autoconf
./configure \
--prefix=/usr/local/pgsql \
--sysconfdir=/var/Settings/PgSQL \
--localstatedir=/var/Process \
--with-docdir=/var/Documentation/html/PgSQL \
--mandir=/var/man \
--enable-shared --disable-static \
--disable-debug --enable-cassert \
--with-template=darwin \
--with-pgport=5432 \
--enable-thread-safety \
--with-maxbackends=1024 \
--with-perl \
--with-java \
--with-pam \
--with-python \
--with-rendezvous \
--with-openssl \
--with-includes="/usr/local/ssl/include /usr/local/include" \
--with-libraries="/usr/local/ssl/lib /usr/local/lib" \
--with-tcl \
--with-tclconfig=/Library/Frameworks/Tcl.framework \
--with-tkconfig=/Library/Frameworks/Tk.framework \
--enable-nls
make
make install
cheers,
richard
OpenMacNews <OpenMacNews@speakeasy.net> writes:
> reading here, it seems builds on 'virgin' Tiger are behaving themselves ...
The short answer seems to be "when you update to 10.4, don't forget to
update to Xcode 2 as well".
regards, tom lane
hi tom, > OpenMacNews <OpenMacNews@speakeasy.net> writes: >> reading here, it seems builds on 'virgin' Tiger are behaving themselves ... > > The short answer seems to be "when you update to 10.4, don't forget to > update to Xcode 2 as well". > > regards, tom lane does it make sense to have configure check for min req'ts of xcode2 if os >= v10.4? cheers, richard
OpenMacNews <OpenMacNews@speakeasy.net> writes:
>> The short answer seems to be "when you update to 10.4, don't forget to
>> update to Xcode 2 as well".
> does it make sense to have configure check for min req'ts of xcode2 if os >=
> v10.4?
No, I don't think so. There is such an astonishing variety of ways to
break your system, on so many different platforms, that we cannot hope
to check them all. If this failure were Postgres-specific then yes,
but the previous report is that it breaks lots of things.
regards, tom lane
> OpenMacNews <OpenMacNews@speakeasy.net> writes: >>> The short answer seems to be "when you update to 10.4, don't forget to >>> update to Xcode 2 as well". > >> does it make sense to have configure check for min req'ts of xcode2 if os >= >> v10.4? > > No, I don't think so. There is such an astonishing variety of ways to > break your system, on so many different platforms, that we cannot hope > to check them all. If this failure were Postgres-specific then yes, true enuf in general ... but _this_ proposed check would really be just a 'did you do a complete OS install (including XCode 2)?' check, rather than any one particular 'widget' etc. have no idea HOW to check for XCode2 install other than looking in /Library/Receipts ... then again, a comment i the INSTALL/README would/should go just as far! > but the previous report is that it breaks lots of things. all in all, it's been relatively well behaved for me so far ... <keeping fingers crossed!> cheers, richard