From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: failing to build preproc.c on solaris with sun studio |
Date: | 2022-09-04 14:55:43 |
Message-ID: | 1732827.1662303343@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2022-09-04 Su 09:56, Tom Lane wrote:
>> You would need to make the ecpg-check step
>> conditional, though, so it's moot: we'd have to fix the buildfarm
>> first in any case, unless it's default-enabled which would seem
>> a bit odd.
> *nod*
I guess we could proceed like this:
1. Invent the --with option. Temporarily make "make check" in ecpg
print a message but not fail if the option wasn't selected.
2. Update buildfarm client to recognize the option and skip ecpg-check
if not selected.
3. Sometime down the road, after everyone's updated their buildfarm
animals, flip ecpg "make check" to throw an error reporting that
ecpg wasn't built.
There'd need to be a separate discussion around how much to
encourage buildfarm owners to add --with-ecpg to their
configurations. One thing that would make that easier is
adding --with-ecpg as a no-op option to the back branches,
so that if you do want it on it doesn't have to be done
with a branch-specific test. (I guess packagers might
appreciate that too.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2022-09-04 15:06:14 | Re: failing to build preproc.c on solaris with sun studio |
Previous Message | Andrew Dunstan | 2022-09-04 14:11:48 | Re: failing to build preproc.c on solaris with sun studio |