autoconf-patches
[Top][All Lists]
Advanced

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

Re: New substitution: top_build_prefix


From: Benoit Sigoure
Subject: Re: New substitution: top_build_prefix
Date: Fri, 16 Nov 2007 20:09:51 +0100

On Nov 15, 2007, at 10:30 PM, Ralf Wildenhues wrote:

* Eric Blake wrote on Sat, Nov 10, 2007 at 08:20:27PM CET:
According to Ralf Wildenhues on 11/10/2007 4:00 AM:

Hmm, do you think I could make the version comparison be against
`2.61a.265'?

Yes, that will work, thanks to my recent fix to m4_version_unletter...

 Do you see a more straightforward way to find out whether
Autoconf substitutes top_build_prefix, i.e., can I access `autom4te
--trace' results from within macro files? I could define a helper macro
in Autoconf, but that wouldn't feel much nicer either.

although I kind of like Benoit's suggestion of also providing a witness macro in autoconf, so that the test can be made independent of whether the
patch is backported to earlier autoconf versions.

OK.  Thanks for the reviews, Benoit and Eric.  This is what I've added
to Autoconf.

Another nitty gritty detail: should I leave in the version check >= 2.62
in Libtool so that future Autoconf versions will not need to carry
around the witness macro baggage?

I don't get it. What's the point of introducing this witness macro if it's not to use it in Libtool? Within 3 or 4 years, a version check will probably be enough, but in the mean time, I think we do better use the witness macro.

--
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory


Attachment: PGP.sig
Description: This is a digitally signed message part


reply via email to

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