[Top][All Lists]

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

Re: Checking versions and defining macros

From: Ralf Wildenhues
Subject: Re: Checking versions and defining macros
Date: Thu, 6 Mar 2008 08:00:58 +0100
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

Hello Jason,

let's please limit replies to the autoconf list, thanks.

* Jason Curl wrote on Wed, Mar 05, 2008 at 06:47:04AM CET:
> To achieve my goals, I've borrowed some of the internals of the auto*  
> tools (and libtool). I'd like to somehow check the version of the  
> autotools during "autoreconf" time and include macros specific to a  
> particular version. If I see a version that I haven't tested with, then  
> I'd like to print a warning that something needs to be looked at (i.e.  
> update my macros). This will allow me especially to upgrade to  
> libtool-2.2 and play with it, while knowing it will always work with 
> 1.5.24.
> A summary of what I've had to hack:
> AC_CHECK_LIB: borrowed from here for the Solaris networking features
> AC_CHECK_DECL: Disable printing, to encapsulate in my own scripts
> AC_PROG_LD: Would die if it couldn't find LD, rather than allow my  
> to provide an alternate

Not sure what your question is.  Autoconf minimum version can be
required with AC_PREREQ, its exact version is
m4_defn([m4_PACKAGE_VERSION]).  Automake minimum version can be required
with AM_INIT_AUTOMAKE.  Libtool minimum version can be required with
LT_PREREQ (starting from 2.2).  To rule out earlier versions, you can
see whether LT_PREREQ is defined: m4_ifdef([LT_PREREQ], [...]).


reply via email to

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