Re: Raising our compiler requirements for 9.6

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Raising our compiler requirements for 9.6
Date: 2015-08-06 14:31:53
Message-ID: 20150806143153.GA12526@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-08-06 10:29:39 -0400, Robert Haas wrote:
> On Thu, Aug 6, 2015 at 3:09 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > It really doesn't. It's just fallout from indirectly including lwlock.h
> > which includes an atomic variable. The include path leading to it is
> >
> > In file included from /home/andres/src/postgresql/src/include/storage/lwlock.h:19:0,
> > from /home/andres/src/postgresql/src/include/storage/lock.h:18,
> > from /home/andres/src/postgresql/src/include/access/tuptoaster.h:18,
> > from /home/andres/src/postgresql/src/bin/pg_resetxlog/pg_resetxlog.c:49:
> > /home/andres/src/postgresql/src/include/port/atomics.h:41:2: error: #error "THOU SHALL NOT REQUIRE ATOMICS"
> > #error "THOU SHALL NOT REQUIRE ATOMICS"
>
> Isn't that #include entirely superfluous?

Which one?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-08-06 14:33:06 Re: 9.5 release notes
Previous Message Robert Haas 2015-08-06 14:29:39 Re: Raising our compiler requirements for 9.6