Re: [HACKERS] New s_lock.h fails on HPUX with gcc - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] New s_lock.h fails on HPUX with gcc
Date
Msg-id 199807181459.KAA09419@candle.pha.pa.us
Whole thread Raw
In response to New s_lock.h fails on HPUX with gcc  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> ... because the conditional structure assumes that pgsql will only be
> built with non-gcc compilers on HPUX.
>
> This is an entirely bogus assumption not only for HPUX, but for any
> other architecture that has gcc available.
>
> To be able to compile, I just duplicated the "#if defined(__hpux)"
> block into the "#if defined(__GNUC__)" part of the file, but that's
> a pretty grotty hack.  I think that the right way to structure the
> file is just this:

I have moved platforms that have have common code for gcc and non-gcc to
their own section of s_lock.h.  Should make things easier.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] New s_lock.h fails on HPUX with gcc
Next
From: Massimo Dal Zotto
Date:
Subject: Re: [HACKERS] two records with same oid, freak accident?