On Fri, Aug 24, 2018 at 02:46:07PM -0700, Andres Freund wrote:
> On 2018-08-24 14:35:18 -0700, Peter Geoghegan wrote:
> > On Fri, Aug 24, 2018 at 2:15 PM, Andres Freund <andres@anarazel.de> wrote:
> > > Do they persist after you do re-configure? If so, could you send your config.log?
> >
> > I should point out to Bruce that this is clearly related to commit
> > 143290efd0795b61ed2c8358fc1767e799140047.
>
> Yes, but the preceding commit (d9dd406fe281d22d5) should've added the
> -std=gnu99, if required, the message complains about - the fact that it
> didn't seems to indicate that either configure didn't run (a bit odd, I
> think it should automatically trigger), or something weird is up (hence
> config.log).
Since no one else was seeing this problem, I started digging, and I have
found it. I narrowed it to down to this line in Makefile.custom
CC=ccache gcc
I thought the problem was that ccache was not detecting the
configuration change, but in fact I had to manually change this line to:
CC=ccache gcc -std=gnu99
so I am good now. :-) (I don't know any way to cleanly add ccache to
CC without hard-coding what configure set it to.)
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +