building trunk fails due to C++

[Gary Funck]

On 11/09/11 14:22:22, Steve Kargl wrote:
> > Besides bootstrapping, you could use --disable-libitm or it might also 
> > work to specify --disable-build-poststage1-with-cxx which also saves you 
> > from building the C++ compiler if you don't want it.
> 
> Doing a full bootstrap adds 3+ hours on my laptop.  Oh well, I 
> guess this is the price of progress.

It gots much worse, with --enable-checking=all in combination with
--enable-build-poststage1-with-cxx (the default, if c++ is built,
and --enable-bootstrap is asserted).

In fact, a build started last night on fast server hardware has yet
to finish.

This particular compilation (insn-emit.c) has been running for
5.5 hours.  Typically, a full bootstrap (with minimal checks) would
finish in much less than 30 minutes on this server.

Has anyone tried a full bootstrap with c,c++ and --enable-checking=all?
Were you successful?  How long did it take to complete?

I haven't looked into this in detail, however, I wonder that if the
C++ compiler is used for final build, whether the build/make will
honor CFLAGS or CXXFLAGS?

Presumably the latter (CXXFLAGS).  This seems like a potentially
surprising side effect, if true.