Thread: Install: Undefined symbol `_TAS'

I've got an installation problem:

OpenBSD 2.6 - gmake 3.78.1 - Postgres 6.5.3 (new install)

storage/SUBSYS.o: Undefined symbol `_TAS' referenced from text segment
collect2: ld returned 1 exit status
make[1]: *** [postgres] Error 1
make: *** [all] Error 2

Frank

Frank Bax <fbax@execulink.com> writes:
> I've got an installation problem:
> OpenBSD 2.6 - gmake 3.78.1 - Postgres 6.5.3 (new install)

> storage/SUBSYS.o: Undefined symbol `_TAS' referenced from text segment

Hm.  tas() is a machine-dependent subroutine for low-level spinlocking.
It's typically provided as a macro in src/include/storage/s_lock.h
or a function in src/backend/storage/buffer/s_lock.c; some platforms
have assembly-coded versions in src/backend/port/tas/.  It sounds like
for some reason none of the provided alternatives are getting compiled
on your platform.  Please dig through the #ifdefs in those files and
figure out what needs to be changed to make it work on your setup.

(A likely possibility is that configure misidentified your platform;
did you notice whether it printed a reasonable platform ID?)
        regards, tom lane

On Fri, Feb 04, 2000 at 01:48:21AM -0500, Tom Lane wrote:
> Frank Bax <fbax@execulink.com> writes:
> > I've got an installation problem:
> > OpenBSD 2.6 - gmake 3.78.1 - Postgres 6.5.3 (new install)
> 
> > storage/SUBSYS.o: Undefined symbol `_TAS' referenced from text segment

OpenBSD 2.6 includes Postgres 6.5.3 in its ports collection, which
fixes this.

> Hm.  tas() is a machine-dependent subroutine for low-level spinlocking.
> It's typically provided as a macro in src/include/storage/s_lock.h
> or a function in src/backend/storage/buffer/s_lock.c; some platforms
> have assembly-coded versions in src/backend/port/tas/.  It sounds like
> for some reason none of the provided alternatives are getting compiled
> on your platform.  Please dig through the #ifdefs in those files and
> figure out what needs to be changed to make it work on your setup.
> 
> (A likely possibility is that configure misidentified your platform;
> did you notice whether it printed a reasonable platform ID?)

--vince