Обсуждение: Re: [HACKERS] snapshot won't compile on irix6.2
Has anyone confirmed these problems under Irix? > Hi, > > i have just grabbed the 6.3 snapshot and tried to compile it on irix 6.2 - > without success. > > The following errors occurred: > > 1) configure fails > > % ./configure > [...] > linking ./backend/port/tas/i386_solaris.s to backend/port/tas.s > linking ./backend/port/dynloader/irix5.c to backend/port/dynloader.c > configure: error: ./backend/port/dynloader/irix5.c: File not found This seems a little fundamental!!! > > > 2) compiling the backend fails: > in src/backend the gcc call > gcc -mabi=64 -o postgres access/SUBSYS.o bootstrap/SUBSYS.o > catalog/SUBSYS.o commands/SUBSYS.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/SUBSYS.o > rewrite/SUBSYS.o storage/SUBSYS.o tcop/SUBSYS.o utils/SUBSYS.o > ../utils/version.o -64 -lPW -lcrypt -lm -lbsd -lreadline -lhistory > -ltermcap -lcurses > > returns > [...] > ld64: ERROR 33: Unresolved text symbol "S_INIT_LOCK" -- 1st referenced by > storage/SUBSYS.o. > ld64: ERROR 33: Unresolved text symbol "S_UNLOCK" -- 1st referenced by > storage/SUBSYS.o. > ld64: ERROR 33: Unresolved text symbol "S_LOCK" -- 1st referenced by > storage/SUBSYS.o > > > these functions just seem to be implemented for linux/alpha ?? I'm generally a little dubious when people report a problem in actually compiling 'cos of the Irix 6.x bug in ld. However, this guy is using gcc, not native Irix cc/ld > Fuad Abdallah > Max-Planck-Institut fuer Zuechtungsforschung / ZWDV > Tel.: 0221/5062-739 / Priv: 0221/584563 > With any luck I should have a bit of time next week to do some testing under Irix - things have been rather hectic the last few weeks. Andrew ---------------------------------------------------------------------------- Dr. Andrew C.R. Martin University College London EMAIL: (Work) martin@biochem.ucl.ac.uk (Home) andrew@stagleys.demon.co.uk URL: http://www.biochem.ucl.ac.uk/~martin Tel: (Work) +44(0)171 419 3890 (Home) +44(0)1372 275775
On Mon, 2 Feb 1998, Andrew Martin wrote: > > [...] > > linking ./backend/port/tas/i386_solaris.s to backend/port/tas.s > > linking ./backend/port/dynloader/irix5.c to backend/port/dynloader.c > > configure: error: ./backend/port/dynloader/irix5.c: File not found > This seems a little fundamental!!!' Fixed now... > > returns > > [...] > > ld64: ERROR 33: Unresolved text symbol "S_INIT_LOCK" -- 1st referenced by > > storage/SUBSYS.o. > > ld64: ERROR 33: Unresolved text symbol "S_UNLOCK" -- 1st referenced by > > storage/SUBSYS.o. > > ld64: ERROR 33: Unresolved text symbol "S_LOCK" -- 1st referenced by > > storage/SUBSYS.o > > > > > > these functions just seem to be implemented for linux/alpha ?? > I'm generally a little dubious when people report a problem in actually > compiling 'cos of the Irix 6.x bug in ld. However, this guy is using > gcc, not native Irix cc/ld From include/storage/s_lock.h: #if defined(irix5) Using tools/ccsym, what shoudl this be set to. There is no longer any concept of a "port" at the Makefile level, and hasn't been for over a month now...From henceforth, its either determined based on what configure knows about, or the compiler itself...in this case, tools/ccsym will have to be used to determine what the compiler defines internally and the settings changed...