A clue for the libstdc++ problem.

[Alexandre Oliva]

On Apr  1, 2001, "H . J . Lu" <hjl@lucon.org> wrote:

> 	* ltcf-cxx.sh: Make sure we never use g++ for the shared
> 	libstdc++-v3.

This is outrageously misleading.  BTW, you've duplicated Zack's
investigative work, and the patch for the top-level Makefile.in I
wrote on Friday to address his findings hasn't worked, it seems, but
it's the Makefile.in that has to be fixed.  Maybe with some
cooperation from the top-level configure.in, for example, setting a
different CXX_FOR_TARGET for use for libstdc++-v3.  But this still
wouldn't fix problem of taking the libstdc++-v3 flags created only
after libstdc++-v3 is configured.  I'm still aiming at a
single-CXX_FOR_TARGET solution.  The tricky thing is how to defer the
evaluation of CXX_FOR_TARGET.

-- 
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