pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: David Steele <david@pgmasters.net>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Craig Ringer <craig@2ndquadrant.com>
Subject: Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c)
Date: Fri, 24 Aug 2018 12:10:34 -0400
Message-ID: <15587.1535127034@sss.pgh.pa.us> (raw)
In-Reply-To: <20180824154623.i32aryx4bzfa4gxu@alap3.anarazel.de>
References: <1d5946a3-aa85-a3ec-c8aa-b3e9b66dd5d9@commandprompt.com>
	<20180821204936.tqdmjolkoo2sv5og@alap3.anarazel.de>
	<303572b3-89a5-6177-d46a-e23b2b4d6caa@2ndQuadrant.com>
	<20180821232952.ixj6kgccoqcjp5gf@alap3.anarazel.de>
	<CANFyU94+wn2iN_ry=2SZFzxdFP6vAHA2+K0uhyyCS4YQWyyrxw@mail.gmail.com>
	<20180822120211.prl6uxspai4lahfs@alap3.anarazel.de>
	<20180823000905.fjthfohmczss4fiw@alap3.anarazel.de>
	<20180823013134.3h4j62eeiaibpgvo@alap3.anarazel.de>
	<eedbe1a9-1d3f-e878-7695-fe9b529f3239@2ndquadrant.com>
	<20180824014434.qourppnik7bmsib6@alap3.anarazel.de>
	<20180824154623.i32aryx4bzfa4gxu@alap3.anarazel.de>

Andres Freund <andres@anarazel.de> writes:
> I'd like to change it so it doesn't enforce C89 compliance across the
> board, but instead enforces the relevant standard. For that I'd need to
> change CFLAGS per-branch in the buildfarm. Is that possible already? Do
> I need two different config files?

I just did that on dromedary, with a stanza like this at the bottom:

if ($branch eq 'HEAD' or $branch ge 'REL_12')
{
        $conf{config_env}->{CC} = 'ccache gcc -std=c99';
}
else
{
        $conf{config_env}->{CC} = 'ccache gcc -ansi';
}

			regards, tom lane




view thread (37+ messages)  latest in thread

Message-ID: <15587.1535127034@sss.pgh.pa.us>
Permalink:  ../15587.1535127034@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15587.1535127034@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, andrew.dunstan@2ndquadrant.com, sandeep.thakkar@enterprisedb.com, peter.eisentraut@2ndquadrant.com, jd@commandprompt.com, thomas.munro@enterprisedb.com, david@pgmasters.net, pgsql-hackers@lists.postgresql.org, craig@2ndquadrant.com
  Subject: Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c)
  In-Reply-To: <15587.1535127034@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox