Re: compilation on sparc_solaris - Mailing list pgsql-hackers

From Shiby Thomas
Subject Re: compilation on sparc_solaris
Date
Msg-id 199802030140.UAA04745@cise.ufl.edu
Whole thread Raw
In response to Re: compilation on sparc_solaris  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: compilation on sparc_solaris  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
=> On Mon, 2 Feb 1998, Shiby Thomas wrote:
=>
=> > Hi,
=> >
=> > It looks like the compilation problem on sparc_solaris is due to some
=> > inconsistencies in the Makefiles. The -D$(PORTNAME) is not passed in
=> > CFLAGS. I made the foll. changes and it compiled fine.
=>
=>     I hate to ask, but what version is the port for?  We already
=> removed all the PORTNAME stuff for v6.3 ;(
=>
Its the latest snapshot on Feb 2. Without the PORTNAME, flag, it didn't compile
when I tried.
gcc -o postgres access/SUBSYS.o bootstrap/SUBSYS.o catalog/SUBSYS.o
commands/SUB
SYS.o executor/SUBSYS.o lib/SUBSYS.o libpq/SUBSYS.o main/SUBSYS.o
nodes/SUBSYS.o
 optimizer/SUBSYS.o parser/SUBSYS.o port/SUBSYS.o postmaster/SUBSYS.o
regex/SUBS
YS.o rewrite/SUBSYS.o storage/SUBSYS.o tcop/SUBSYS.o utils/SUBSYS.o
../utils/ver
sion.o -lgen -lcrypt -lnsl -lsocket -ldl -lm -lreadline -ltermcap -lcurses
Undefined           first referenced
 symbol                 in file
tas                                 storage/SUBSYS.o
ld: fatal: Symbol referencing errors. No output written to postgres

It also gave the foll. warning while compiling in the backend/storage dir
gcc -I../../../include -I../../../backend  -I../../../backend/port/sparc_solari
s
  -Wall -Wmissing-prototypes -Dsparc_solaris -I../..    -c spin.c -o spin.o
../../../include/storage/s_lock.h:123: warning: `tas' declared `static' but
neve
r defined

--shiby



pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] (: JDBC+(Sun ~3:pm MST) CVS :) -also question about regression tests
Next
From: The Hermit Hacker
Date:
Subject: Re: compilation on sparc_solaris