Re: Problem building initdb on sparc10

From: "Averbukh Stella" <Stella(dot)Averbukh(at)arbitron(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-admin(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: Problem building initdb on sparc10
Date: 2006-05-30 15:34:15
Message-ID: C9995BA6EBD30240A86235B6FCCF5A6807639495@ARBEX2KC.arbitron.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

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.

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: <mailto:stella(dot)averbukh(at)arbitron(dot)com>

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, May 30, 2006 11:29 AM
To: Averbukh Stella
Cc: pgsql-admin(at)postgresql(dot)org; pgsql-hackers(at)postgresql(dot)org; Bruce
Momjian
Subject: Re: [ADMIN] Problem building initdb on sparc10

"Averbukh Stella" <Stella(dot)Averbukh(at)arbitron(dot)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

______________________________________________________________________
This e-mail has been scanned by Arbitron's Email Content Service.
______________________________________________________________________

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2006-05-30 15:44:08 Re: Separating Databases on Different Partitions
Previous Message Tom Lane 2006-05-30 15:29:20 Re: Problem building initdb on sparc10

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-05-30 15:35:12 Re: plperl's ppport.h out of date?
Previous Message Mandy Abrahams 2006-05-30 15:29:51 Looking for Postgres Developers to fix problem