> > 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.
yeah. I just use AC_CANONICAL_SYSTEM now.
> > ***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
done, thanks,
> 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.
hmm. well, i noticed the AC_PROG_CXX stuff requires libstdc++: so does
AC_PROG_CXXCPP.... obviously, this is less useful to me as I'm concerned
with the building of said libstdc++
:)
what i was doing (in another context) to get around this was
gcc -x c++ to test the c++ compiler, and
g++ to test the c++ compiler and library.
Anyway. It would be cool if there could be a
AC_PROG_CXX
AC_PROG_LIBSTDCXX
so I could use the standard autocont macros in libstdc++'s configure
scripts...
-benjamin
