On Jul 26, 2000, Benjamin Kosnik <[EMAIL PROTECTED]> wrote:
>> 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++
Ahh, good point. I was referring to the C-only stuff. But the same
problem applies when configuring newlib. I wonder how the newlib guys
solved it. [time passes] Yes, the stuff you copied from libgcj was
first created in newlib.
It seems to me that what we really need in autoconf is some way for
the configure.in script to tell autoconf the package being configured
is a bootstrap component, so that configure doesn't require the
compiler to be fully functional.
--
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
