V3 Configury

Benjamin Kosnik bkoz@redhat.com
Tue Jan 23 09:33:00 GMT 2001


> > I'm going to group these functions into bigger amalgamations and just
> > produce all-or-nothing results for the whole amalgamation.  That
> > should reduce the per-function cost substantially.
> 
> Like Gaby says, no bet.  :-) 

Go ahead and try this approach though. Let's see what breaks. If nothing 
breaks, Mark wins!

I'd rather group than disable tests due to what we know about the os. 

> > Also, <ctype> detection alone takes a long time (over a minute) to
> > work out.  Why are we doing this with autoconf (in a rather hacky way,
> > involving checking for funny symbols in ctype.h) rather than using
> > configure.target, like we do for other obscure properties on the
> > target?  I'm going to change that too.
> 
> The autoconf tests predate the existence of config.target by a long time.
> Moving them seems safe to me.

Ditto. Thanks!

benjamin


More information about the Libstdc++ mailing list