On May 10, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> But it seems hard to me to cope with the various uses of autoheader.
It's absolutely essential that autoconf keeps working with
multi-header projects. GCC needs it badly to separate build
properties from host properties from target properties (maybe I've got
one item too much, but you get the idea :-). Because, in some
cross-compilation environments, some files have to be compiled more
than once, with different compilers and for different targets, the
configuration files they use must be kept separate.
We might just say than, in this case, GCC can't use autoheader, but
I'd rather find a way to allow people to generate multiple header
files with autoheader, even if this means indicating in each 3- (or
4-)argument AC_DEFINE which header file(s) should contain the
definition, and check all output header files before complaining that
a certain AC_DEFINE has no corresponding #undef.
--
Alexandre Oliva Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
