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 574B19FA5FB; Tue, 30 May 2006 12:29: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 28225-09; Tue, 30 May 2006 12:29:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id C80E29FA5E2; Tue, 30 May 2006 12:29:23 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4UFTLFO024190; Tue, 30 May 2006 11:29:21 -0400 (EDT) To: "Averbukh Stella" cc: pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org, Bruce Momjian Subject: Re: Problem building initdb on sparc10 In-reply-to: References: Comments: In-reply-to "Averbukh Stella" message dated "Tue, 30 May 2006 09:21:32 -0400" Date: Tue, 30 May 2006 11:29:20 -0400 Message-ID: <24188.1149002960@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/415 X-Sequence-Number: 21947 "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 > -Winline -Wendif-labels -fno-strict-aliasing initdb.o > -L../../../src/port -lpgport -L../../../src/interfaces/libpq -lpq > -L../../../src/port -Wl,-R/postgres/lib -L/lib -L/usr/lib > -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 -lpgport > -lz -lrt -lresolv -lgen -lsocket -lnsl -ldl -lm -o initdb > Undefined first referenced > symbol in file > sigmask ../../../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. 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