[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

["phil at nwl dot cc" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #23 from phil at nwl dot cc  2010-01-15 22:32 -------
(In reply to comment #22)
> (In reply to comment #21)
> > (In reply to comment #18)
> > > Just build everything with default configure options, then go inside the
> > > libstdc++-v3 *build* dir and type 'make check'.
> > 
> > Ah, hmm. Well, having to compile everything in order to run the tests using an
> > external compiler is a bit of a bummer, isn't it?
> 
> Maybe there is a communication problem here: I meant, *the whole GCC*,

Yes, it seems so.

> normally, with no special options, to keep things simple. If you want, you can
> exclude java, which normally takes a while, and fortran, and objective c, the
> languages you don't need in other terms: just pass --enable-languages=c++ and
> nothing else.

What we want to do is to run the libstdc++ testsuite with my
distribution-provided g++, in order to see whether it's generally broken or
not, right?

And what I'm criticising here is that I have to compile *anything* of the
gcc-sources in order to run the testsuite. I see no sense in building any
binaries at all, since I already have all binaries (executables as well as
libraries) in order to run the tests?!


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734