autoconf
[Top][All Lists]
Advanced

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

Re: Autoconf 2.52 is released


From: Paul Eggert
Subject: Re: Autoconf 2.52 is released
Date: Tue, 24 Jul 2001 14:48:34 -0700 (PDT)

> From: Lars Hecking <address@hidden>
> Date: Tue, 24 Jul 2001 19:36:00 +0100
>  
>  Some hints on how to have configure.in compatible with both versions
>  would be more than welcome.

The most important bit of advice is to stick only to 2.13-style
features, and to avoid 2.13's bugs.  (That last bit is the part I
found the most difficult.  :-)

One of my biggest problems was the {host,target,build}_alias mess of
Autoconf 2.13.  I'm afraid that I don't have a good answer for that
one.  I worked around this problem by removing AC_CANONICAL_HOST from
my configure.in files.  This turned out to be easier than I thought it
would be.  But it might not suffice for other people, and perhaps it
would be helpful to come up with some transition advice here.

To work around intractable problems like that, perhaps you could use
code that looks like this:

   ifdef([m4_ifdef], [
     echo autoconf 2.50 or newer
   ], [
     echo autoconf 2.13 or older
   ])

(I was a bit surprised that this worked -- isn't 2.5x supposed to
rename `ifdef'?)

I'd hate to have to resort to that, but it might be better than
sticking with 2.13 only.


>  One problem now is that 2.5x creates configure from old, 2.1x style
>  configure.in without errors, implying that they work, while in fact
>  they don't.

That's a bit too strong, as it worked for me.  It depends on the
configure.in file.  The question is whether it's relatively easy to
write configure.in files that work with both 2.1x and 2.5x.



reply via email to

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