Why not stick with what you have? It may be ugly, but
any Autoconfish replacement would be just as ugly, if
not uglier. And what you have works now.
On 4/13/11 3:59 PM, Eric Blake wrote:
> On 04/13/2011 03:49 PM, Philip Prindeville wrote:
>> It is sometimes useful to be able to detect the compiler version (as in the
>> case of GCC 4.2 doing some fairly aggressive optimization that breaks
>> fragile code).
> Thanks for the report.
>
>> How abo
On 04/13/2011 11:02 AM, Tom Lane wrote:
> If the intended use is only for ansi2knr, I'd even argue that it
> should be off by default ... how many people care about ansi2knr
> anymore?
Nobody. It would be fine to remove the ansi2knr stuff from Autoconf.
On 04/13/2011 03:49 PM, Philip Prindeville wrote:
> It is sometimes useful to be able to detect the compiler version (as in the
> case of GCC 4.2 doing some fairly aggressive optimization that breaks fragile
> code).
Thanks for the report.
>
> How about something like:
>
> AC_GCC_VERSION(VER,
It is sometimes useful to be able to detect the compiler version (as in the
case of GCC 4.2 doing some fairly aggressive optimization that breaks fragile
code).
How about something like:
AC_GCC_VERSION(VER, MATCHING-VERSION, [ NON-MATCHING-VERSION ])
so I could do something like:
AC_GCC_VERSI
Eric Blake writes:
> On 04/13/2011 11:31 AM, Tim Wallace wrote:
>> This is a bug discovered when trying to build postgresql 9.0.3 on Redhat
>> Enterprise Linux 5. If env var U is set, it fails, as pointed out by
>> the Postgres maintainer.
> The issue still exists in autoconf 2.68 (and autoconf.
On 04/13/2011 11:31 AM, Tim Wallace wrote:
> This is a bug discovered when trying to build postgresql 9.0.3 on Redhat
> Enterprise Linux 5. If env var U is set, it fails, as pointed out by
> the Postgres maintainer. I guess it's autoconf 2.59, and I'm guessing
> you're past that now, so possibly
This is a bug discovered when trying to build postgresql 9.0.3 on Redhat
Enterprise Linux 5. If env var U is set, it fails, as pointed out by
the Postgres maintainer. I guess it's autoconf 2.59, and I'm guessing
you're past that now, so possibly it has already been fixed. Baffling
bug, thoug