Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] 6.5.2 broken on alpha/Tru64 Unix 4.0d/cc

From: "Pedro J(dot) Lobo" <pjlobo(at)euitt(dot)upm(dot)es>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL bugs mailing list <pgsql-bugs(at)postgreSQL(dot)org>, PostgreSQL ports mailing list <pgsql-ports(at)postgreSQL(dot)org>
Subject: Re: [BUGS] 6.5.2 broken on alpha/Tru64 Unix 4.0d/cc
Date: 1999-10-11 08:37:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-ports
On Fri, 8 Oct 1999, Tom Lane wrote:

>Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
>> New code in Makefile.alpha is:
>> 	/* some platforms define __alpha, but not __alpha__ */
>> 	#if defined(__alpha) && !defined(__alpha__)
>> 	#define __alpha__
>> 	#endif
>OK, so we're going to standardize on __alpha__ to recognize that
>platform?  OK by me, unless the Alpha users know a reason not to.

I don't see any. The only problem I can see is that __alpha (or __alpha__)
used to mean "Alpha/Tru64 Unix", and this is no longer true because of
Alpha/Linux. If there is any place in the code that's valid only for
Alpha/Tru64, then __osf__ should be used.

For example, s_lock.h uses the msem_xxx functions to implement spinlocks
when gcc is not used. These functions are related to msemaphores, which
are semaphores that live in shared memory segments (or "mmap"ed files). I
don't know wheter this group of functions is specific to Tru64 Unix, but
at least FreeBSD doesn't have them. If Alpha/Linux doesn't have them, then
__osf__ should be used there instead of __alpha__ (or at least a
combination of both).



Pedro José Lobo Perea                   Tel:    +34 91 336 78 19
Centro de Cálculo                       Fax:    +34 91 331 92 29
E.U.I.T. Telecomunicación               e-mail: pjlobo(at)euitt(dot)upm(dot)es
Universidad Politécnica de Madrid
Ctra. de Valencia, Km. 7                E-28031 Madrid - España / Spain

In response to

pgsql-ports by date

Next:From: Thomas LockhartDate: 1999-10-11 15:12:33
Subject: Re: [PORTS] 'current'::datetime
Previous:From: Brian EdmondsDate: 1999-10-10 15:26:05
Subject: Linux 2.2.12 SMP build success report

pgsql-bugs by date

Next:From: Vitaly PiniyginDate: 1999-10-12 09:12:33
Subject: Pg module "eats" environment
Previous:From: Tom LaneDate: 1999-10-10 16:13:07
Subject: Re: [BUGS] Three Regression Test Problems involving dates

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group