pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Averbukh Stella <Stella.Averbukh@arbitron.com>
Cc: pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org, Bruce Momjian <pgman@candle.pha.pa.us>
Subject: Re: Problem building initdb on sparc10
Date: Tue, 30 May 2006 11:29:20 -0400
Message-ID: <24188.1149002960@sss.pgh.pa.us> (raw)
In-Reply-To: <C9995BA6EBD30240A86235B6FCCF5A6807639490@ARBEX2KC.arbitron.com>
References: <C9995BA6EBD30240A86235B6FCCF5A6807639490@ARBEX2KC.arbitron.com>

"Averbukh Stella" <Stella.Averbukh@arbitron.com> 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



view thread (13+ messages)  latest in thread

Message-ID: <24188.1149002960@sss.pgh.pa.us>
Permalink:  ../24188.1149002960@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24188.1149002960@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Stella.Averbukh@arbitron.com, pgman@candle.pha.pa.us
  Subject: Re: Problem building initdb on sparc10
  In-Reply-To: <24188.1149002960@sss.pgh.pa.us>
  References: <C9995BA6EBD30240A86235B6FCCF5A6807639490@ARBEX2KC.arbitron.com> <24188.1149002960@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox