[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_DEFINE problem
From: |
Keith MARSHALL |
Subject: |
Re: AC_DEFINE problem |
Date: |
Fri, 28 Apr 2006 16:48:31 +0100 |
Ralf Wildenhues wrote, quoting Peter Breitenlohner:
>> Isn't this (i.e., aclocal.m4 containing private macros[*] without
>> their sources) something that should be VERY STRONGLY discouraged.
>> After all, running "reautoconf" may (does?) invoke aclocal.
>
> Yes, I agree.
Eh? Quoting autoconf-2.59 documentation:
|To create a `configure' script with Autoconf, you need to write an
|Autoconf input file `configure.ac' (or `configure.in') and run
|`autoconf' on it. If you write your own feature tests to supplement
|those that come with Autoconf, you might also write files called
|`aclocal.m4' and `acsite.m4'.
If I follow this advice, and write `aclocal.m4' myself, then *by
definition*, `aclocal.m4' *is* the source!
Cheers,
Keith.
- Fwd: AC_DEFINE problem, ericdan, 2006/04/28
- Re: AC_DEFINE problem, Ralf Wildenhues, 2006/04/28
- Re: AC_DEFINE problem, ericdan, 2006/04/28
- Re: AC_DEFINE problem, Ralf Wildenhues, 2006/04/28
- Re: AC_DEFINE problem, Peter Breitenlohner, 2006/04/28
- Re: AC_DEFINE problem, Ralf Wildenhues, 2006/04/28
- Re: AC_DEFINE problem,
Keith MARSHALL <=
- Re: AC_DEFINE problem, Ralf Wildenhues, 2006/04/28
- Assinine mailer address mangling (was: AC_DEFINE problem), Keith Marshall, 2006/04/29
- Re: Assinine mailer address mangling (was: AC_DEFINE problem), Bob Proulx, 2006/04/30