This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/41645] Massive failures in parallel test mode
- From: "paolo dot carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Oct 2009 13:52:53 -0000
- Subject: [Bug libstdc++/41645] Massive failures in parallel test mode
- References: <bug-41645-9525@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from paolo dot carlini at oracle dot com 2009-10-09 13:52 -------
Indeed, the system library should not be used at all, but in your example above
the system library *is* used unless you make sure to properly install
everything, set the appropriate LD_LIBRARY_PATH, etc. In other terms, I would
be curious to know what happens if you just build everything, install it, and
then use normally the new compiler, for example to compile and run outside the
testsuite some tests... If everything works, it's just some sort of weird
testsuite issue.
PS: in case you didn't notice already, libtestc++.a is built by
v3-build_support in libstdc++.exp, indeed, the system stuff should not be
involved at all...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41645