On Jul 25, 2000, Benjamin Kosnik <[EMAIL PROTECTED]> wrote:
> on a side note, these are the problems that I'm having with the head
> autoconf: can you please advise?
> configure.in:18: warning: AC_CANONICAL_HOST invoked multiple times
> configure.in:18: warning: AC_CANONICAL_BUILD invoked multiple times
No real problem here, it's just that AC_CANONICAL_HOST now AC_REQUIREs
AC_CANONICAL_BUILD, and AC_CANONICAL_SYSTEM runs the three of them.
No big deal.
> ***BUG in Autoconf--please report*** AC_PROG_CC_G
> ***BUG in Autoconf--please report*** AC_PROG_CC_GNU
> ***BUG in Autoconf--please report*** AC_PROG_CXX_G
> ***BUG in Autoconf--please report*** AC_PROG_CXX_GNU
These macros have never been part of the public API of autoconf, and
they have gained a leading underscore in their names to reflect this
fact.
You may want to add something to acinclude.m4 to make libstdc++-v3
forward compatible, such as:
ifdef([AC_PROG_CC_G],[],[define([AC_PROG_CC_G],defn([_AC_PROG_CC_G]))])
etc
The good news is that, with the changes I've just submitted for the
handling of C{C,XX}_FOR_TARGET et al in the top-level configure, this
will probably no longer be necessary, as long as
target-configure-libstdc++{,-v3} depends on target-all-newlib.
--
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
