On Thu, Feb 07, 2002 at 03:06:59PM -0500, Thomas Dickey wrote:
> On Thu, Feb 07, 2002 at 02:35:04PM +0100, Akim Demaille wrote:
> > >> Anyway, there are so many scripts depending on these names, that
> > >> whatever scheme will be chosen, we will keep them.
> >
> > Thomas> (such as AC_CHECK_LIB ;
On Thu, Feb 07, 2002 at 02:35:04PM +0100, Akim Demaille wrote:
> >> Anyway, there are so many scripts depending on these names, that
> >> whatever scheme will be chosen, we will keep them.
>
> Thomas> (such as AC_CHECK_LIB ;-)
>
> I must have lost the track here. Many people have asked for its
> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes:
>> This has been a default in Autoconf for years. I have a few ideas
>> on how to remove this problem, while at the same time enable the
>> implementation of other features. But it requires severe surgery,
>> which is not possible at
On 7 Feb 2002, Akim Demaille wrote:
> John> it's less surprising that they might change than that documented
> John> behavior might change. (Of course I don't mean that
> John> ac_cv_header_foobar_h is not mentioned in the Autoconf docs, I
> John> mean even the format of the cache variable that
> "John" == John D Burger <[EMAIL PROTECTED]> writes:
John> Lars Hecking:
>> The names are fairly obvious, and there's a section in the autoconf
>> manual that explains them (Results of Tests->Caching Results->Cache
>> Variable Names).
John> Thomas Dickey:
>> Though the mechanism is (has b
Lars Hecking:
> The names are fairly obvious, and there's a section in the autoconf manual
> that explains them (Results of Tests->Caching Results->Cache Variable Names).
Thomas Dickey:
> Though the mechanism is (has been) documented, the convention for several
> macros has changed a couple of
> "Thomas" == Thomas Dickey <[EMAIL PROTECTED]> writes:
Thomas> Though the mechanism is (has been) documented, the convention
Thomas> for several macros has changed a couple of times over
Thomas> autoconf's history. (Apparently they are not so obvious as to
Thomas> prevent maintainers from b
On Tue, Feb 05, 2002 at 05:26:10PM +, Lars Hecking wrote:
> > My question is, are SOME_VAR and SOME_OTHER_VAR things I should set
> > myself in the optional arguments to the AC_CHECK macros, or should I use
> > cache variables? I'm uneasy about using the latter, because I've had
> > trouble
John D. Burger writes:
> I have what I think is a style question:
>
> If I want to do something with the results of autoconf tests in my
> configure script, what's the best way to check these results? For
> instance, say I'd like to do this:
>
> AC_CHECK_LIB(norman, snStackPush)
> AC_CHECK_
I have what I think is a style question:
If I want to do something with the results of autoconf tests in my
configure script, what's the best way to check these results? For
instance, say I'd like to do this:
AC_CHECK_LIB(norman, snStackPush)
AC_CHECK_HEADERS([norman.h])
# Gripe if neith
10 matches
Mail list logo
