This is the mail archive of the
mailing list for the GDB project.
Re: Changing the C/C++ compiler for gdb testsuite runs
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Michael Snyder <msnyder at redhat dot com>
- Cc: gdb at sources dot redhat dot com, Richard dot Earnshaw at arm dot com
- Date: Fri, 11 Jan 2002 10:23:28 +0000
- Subject: Re: Changing the C/C++ compiler for gdb testsuite runs
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> > Is there a way of forcing the GDB testsuite to use a particular compiler
> > that hasn't yet been installed (I have a gcc-3 compiler from a build tree
> > that I'd like to use to run the tests, but I don't particularly want to
> > have to install it first). I've tried running
> > make check
> > with both CC_FOR_TARGET and CC set to point to the compiler, but neither
> > seems to work. There doesn't appear to be anything on this in the gdb
> > internals manual either.
> If you build both gcc and gdb in the same build tree,
> the tests will use the gcc from the build tree.
But since they don't come from the same CVS tree, I can't see how to do
that cleanly without dicking around with the common code directories such
as libiberty and include -- experience has shown that with the public CVS
repositories that is fraught with problems. I have done it in the past,
but it breaks the principal that the sources you are testing are the
sources you are committing, so it isn't really a viable option.