From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: configure fails for perl check on CentOS8 |
Date: | 2019-10-16 12:32:48 |
Message-ID: | 11385.1571229168@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On Tue, Oct 15, 2019 at 6:45 AM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
>> The problematic command line boils down to:
>> $ ./configure --with-perl CFLAGS=-O0
>> It is bash-aliased and survived without being found for a long time on
>> my Cent7 environment, but CentOS8 doesn't allow that.
I don't quite understand why that wouldn't work.
>> By the way, is there any official way to specify options like -O0
>> while configure time?
> CFLAGS=-O0 configure --with-perl ...
The way Horiguchi-san did it has been supported by autoconf for
a good long time now, so I don't think command line syntax is
the issue. Could that CFLAGS setting be interfering with some
feature test in our configure script?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2019-10-16 12:50:17 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |
Previous Message | Tom Lane | 2019-10-16 12:27:57 | Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |