| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Compile failures today |
| Date: | 2018-08-24 22:27:52 |
| Message-ID: | 20180824222752.kkgqvpnud32oocww@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-08-24 18:21:48 -0400, Bruce Momjian wrote:
> 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(at)anarazel(dot)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
Yea, that's a bad idea. You should instead pass CC='ccache gcc' to
configure, rather than doing it Makefile.custom.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-24 22:41:07 | Re: Compile failures today |
| Previous Message | Bruce Momjian | 2018-08-24 22:21:48 | Re: Compile failures today |