| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Raising our compiler requirements for 9.6 |
| Date: | 2015-08-05 15:28:24 |
| Message-ID: | 20150805152824.GK12598@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-08-05 11:23:22 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I'm ok with that too, although I do like the warning at configure
> > time. I'd go with the template approach due to that, but I don't feel
> > strongly about it.
>
> Meh. I did *not* like the way you proposed doing that: it looked far too
> dependent on autoconf internals (the kind that they change regularly).
Hm, I'd actually checked that as_echo worked back till 9.0. But it
doesn't exist in much older releases.
> If you can think of a way of emitting a warning that isn't going to break
> in a future autoconf release, then ok.
echo "$as_me: WARNING: disabling inlining on 32 bit aix due to a bug in xlc" 2>&1
then. That'd have worked back in 7.4 and the worst that'd happen is that
$as_me is empty.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-08-05 16:01:01 | Re: Dependency between bgw_notify_pid and bgw_flags |
| Previous Message | Tom Lane | 2015-08-05 15:23:22 | Re: Raising our compiler requirements for 9.6 |