X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id BC7809FA5E6; Tue, 30 May 2006 12:34:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 27867-09; Tue, 30 May 2006 12:34:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from brightmail.arbitron.net (mail2.arbitron.com [198.40.3.191]) by postgresql.org (Postfix) with ESMTP id 1DD399FA5E2; Tue, 30 May 2006 12:34:22 -0300 (ADT) Received: from arbex2kb.arbitron.com (internal.arbitron.com [198.40.3.64]) by brightmail.arbitron.net (8.12.10/8.12.5) with ESMTP id k4UFYGmm027132; Tue, 30 May 2006 11:34:16 -0400 Received: from ARBEX2KC.arbitron.com ([10.10.200.210]) by arbex2kb.arbitron.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 30 May 2006 11:34:16 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Problem building initdb on sparc10 Date: Tue, 30 May 2006 11:34:15 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] Problem building initdb on sparc10 Thread-Index: AcaD/dT5kVcyRIqWSLq0ZaQrzNtQegAAE1Lg From: "Averbukh Stella" To: "Tom Lane" Cc: , , "Bruce Momjian" X-OriginalArrivalTime: 30 May 2006 15:34:16.0291 (UTC) FILETIME=[829D3330:01C683FE] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/416 X-Sequence-Number: 21948 Hi Tom, Actually I'm building it first time. The system didn't have prior versions of postgreSQL installed. I took postgresql-8.1.3.tar.gz code distribution. =20 I'll try to remove it from the code. Thanks. Stella Averbukh _________________________________ Senior Software Lead, Arbitron Inc. Phone: (410) 312-8387 Fax: (410) 312-8614 e-mail: -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us]=20 Sent: Tuesday, May 30, 2006 11:29 AM To: Averbukh Stella Cc: pgsql-admin@postgresql.org; pgsql-hackers@postgresql.org; Bruce Momjian Subject: Re: [ADMIN] Problem building initdb on sparc10=20 "Averbukh Stella" writes: > I'm building postgresQL on Sparc10 and the build goes fine unil initdb. > /usr/local/bin/gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith=20 > -Winline -Wendif-labels -fno-strict-aliasing initdb.o=20 > -L../../../src/port -lpgport -L../../../src/interfaces/libpq -lpq=20 > -L../../../src/port -Wl,-R/postgres/lib -L/lib -L/usr/lib=20 > -L/usr/local/lib -L/usr/local/ssl/lib -L/platform/SUNW,Ultra-60/lib > -L/usr/sfw/lib/sparcv9 -L/usr/sfw/lib/ -L/usr/local/lib/sparcv9=20 > -lpgport -lz -lrt -lresolv -lgen -lsocket -lnsl -ldl -lm -o initdb=20 > Undefined first referenced symbol in file sigmask=20 > ../../../src/interfaces/libpq/libpq.so > sigblock ../../../src/interfaces/libpq/libpq.so When did you last successfully build PG on this system? I'm guessing you must have been using 7.4 or older, because AFAICS this was broken by this 8.0 change: 2004-01-08 21:02 momjian * doc/src/sgml/libpq.sgml, src/backend/nodes/read.c, src/interfaces/libpq/fe-connect.c, src/interfaces/libpq/fe-print.c, src/interfaces/libpq/fe-secure.c, src/interfaces/libpq/libpq-fe.h, src/interfaces/libpq/libpq-int.h, src/interfaces/libpq/pqsignal.c, src/interfaces/libpq/pqsignal.h: Allow libpq to do thread-safe SIGPIPE handling. This allows it to ignore SIGPIPE from send() in libpq, but terminate on any other SIGPIPE, unless the user installs their own signal handler. =09 This is a minor fix because the only time you get SIGPIPE from libpq's send() is when the backend dies. The code appears to unconditionally assume that sigmask() and sigblock() exist. Not a good assumption. AFAICS pqsignalinquire() isn't even used anywhere (at least not in HEAD), so the simplest answer may be to remove it rather than try to fix it. It's in src/interfaces/libpq/pqsignal.c. regards, tom lane ______________________________________________________________________ This e-mail has been scanned by Arbitron's Email Content Service.=20 ______________________________________________________________________