Re: AC_DEFINE problem

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

 



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.


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux