Re: Allowing printf("%m") only where it actually works

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Allowing printf("%m") only where it actually works
Date: 2018-08-13 05:05:10
Message-ID: alpine.DEB.2.21.1808122229320.8536@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> Indeed, there are hundreds of warnings around "pg_printf_attribute_m"
>> added with gcc 7.3.0 on by ubuntu 18.04 laptop, thanks to 3a60c8ff.
>
> Oh? What warnings exactly? I would not expect any new warnings except
> on platforms where gcc believes the local printf is non POSIX compliant,
> which certainly ought not happen on any non-obsolete Linux.

Hmmm. Strange. The good news, is sthat it does not show anymore. Maybe
this was because I had not done a "configure" before recompiling. Sorry
for the noise.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Toshi Harada 2018-08-13 05:56:33 "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3
Previous Message Amit Kapila 2018-08-13 05:03:21 Re: Explain buffers wrong counter with parallel plans