Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c) - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c)
Date
Msg-id 20180824170229.lm7dkcvz7nfb2wxs@alap3.anarazel.de
Whole thread Raw
In response to Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2018-08-24 12:10:34 -0400, Tom Lane wrote:
> 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';
> }

Thanks, did something similar, mylodon should become green soon. I kinda
was hoping that CFLAGS would directly accept version specific like some
other vars directly...

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: table_privileges view under information_schema doesn't showprivileges on materialized views
Next
From: "Bossart, Nathan"
Date:
Subject: Re: Improve behavior of concurrent ANALYZE/VACUUM