This is the mail archive of the
mailing list for the GCC project.
Re: [www-patch] Testing C++ changes
- From: Jason Merrill <jason at redhat dot com>
- To: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- Cc: gcc-patches at gcc dot gnu dot org, giovannibajo at libero dot it, gerald at pfeifer dot com, mark at codesourcery dot com, tromey at redhat dot com, gdr at integrable-solutions dot net, toa at pop dot agri dot ch, gcc at gcc dot gnu dot org
- Date: Thu, 27 Nov 2003 10:32:22 -0500
- Subject: Re: [www-patch] Testing C++ changes
- References: <200311261435.hAQEZAsV011032@relay.rwth-aachen.de>
On Wed, 26 Nov 2003 15:35:17 +0100 (CET), Volker Reichelt <email@example.com> wrote:
>> And you are neglecting to run the libstdc++ testsuite.
> Sorry. Giovanni told me that this is not necessary. But given Gerald's
> patch, I think you're right.
And I've been at this longer than he has. :)
>> $ rm -rf */libstdc++-v3
> Wouldn't "make clean-target-libstdc++-v3" be enough?
Usually. If there have been configury changes since you last built v3,
sometimes this breaks. Reconfiguring v3 doesn't take long, so I find it
simpler to just remove the directory and start over.
> +make -C gcc cc1plus # (cc1plus.exe for cygwin) build C++ compiler
Also, you don't need this step. all-gcc is implied by