[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[8]: Best practices to detect autoconf version in macro.

From: Konstantin Andreev
Subject: Re[8]: Best practices to detect autoconf version in macro.
Date: Wed, 31 Mar 2010 01:08:50 +0400
User-agent: Thunderbird (Windows/20090302)

On Wen, 30 Mar 2010, Ralf Wildenhues wrote:
Try to abandon all old Autoconf and Automake (if you use both). Go through the 
NEWS files of each of the two packages, take notes for incompatible changes 
(looking up newer constructs in the manual as you go along). Go through your 
build system and adjust.

Unfortunately, this is not an option :(  -  I am not a product (Mozilla) owner.

On Wen, 30 Mar 2010, Eric Blake wrote:
On 03/30/2010 03:13 AM, Konstantin Andreev wrote:
Simultaneously targeting 2.59 and newer is moderately easy, and still supported 
by this list.  Supporting 2.50 and newer is a bit tougher, but not intractable. 
 But simultaneously supporting 2.13 and 2.50+ is MUCH harder, with very few 
people even attempting it.

If m4_version_compare is defined (added in 2.53, documented in 2.62), then use 
it.  Otherwise, you know that you are targeting an older autoconf.

Thanks for all advices and opinions. I'll try to accommodate them to my task.

Best regards,
Konstantin Andreev.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]