On Wednesday 03 February 2010 01:40:06 CeDeROM wrote: > On Wed, Feb 3, 2010 at 4:17 AM, Mike Frysinger wrote: > > i guess the AS_* stuff is new to autoconf-2.64. are people ok with > > requiring that newer version ? > > I think it shoud build also on older autoconf releases - if it could > few branches ago..?
that isnt much of an argument. this generally affects people doing development (as autotools arent used in a distributed package), and generally it's expected that people doing development are a bit more competent in keeping their systems up to date. newer versions of development tools brings newer functionality which is what i leveraged. the unified code i wrote using these new macros is certainly a lot better than what was there before. looking into a bit more, the autoconf output lies. the problem is with only two of the macros ... AS_VAR_APPEND and m4_ifnblank. both of which are easy to provide fallback replacements in acinclude.m4. things seem to work for me with autoconf-2.61+ now. i'm not really concerned with older versions considering 2.61 was released over 3 years ago. -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com
_______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
