From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19026 invoked by alias); 15 Jan 2010 23:07:24 -0000 Received: (qmail 18979 invoked by uid 48); 15 Jan 2010 23:07:11 -0000 Date: Fri, 15 Jan 2010 23:07:00 -0000 Message-ID: <20100115230711.18978.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called" In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "paolo dot carlini at oracle dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-01/txt/msg01932.txt.bz2 ------- Comment #24 from paolo dot carlini at oracle dot com 2010-01-15 23:07 ------- (In reply to comment #23) > 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? Wrong. You can't use one compiler (older, by the way), with a newer libstdc++. > 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?! You don't, you *need* a complete new GCC. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734