Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c)

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c)
Дата
Msg-id 20180824170229.lm7dkcvz7nfb2wxs@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Windows vs C99 (was Re: C99 compliance for src/port/snprintf.c)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Ashutosh Sharma
Дата:
Сообщение: Re: table_privileges view under information_schema doesn't showprivileges on materialized views
Следующее
От: "Bossart, Nathan"
Дата:
Сообщение: Re: Improve behavior of concurrent ANALYZE/VACUUM