On Jul 26, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> It is still problematic: we need the extensions during AC_PROG_CXX for
> the sanity tests, so it must be called beforehand, but since it needs
> the compiler, it must be called afterwards :(
The macro would have to be called first, and it would enable some
conditional behavior in AC_PROG_CXX.
> I can't see how this macro could be optional...
> Hm, well, yes actually, I see how: setting an sh var which
> enables/disables code in AC_PROG_CXX.
I'd rather handle it totally in m4, so that we wouldn't even generate
the sh code if the multi-extension macro isn't used.
This macro would accept a list of extensions the Makefiles are
prepared to handle. If the argument is omitted, autoconf would use a
pre-determined set of extensions.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
