From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1179 invoked by alias); 11 Jan 2002 01:30:18 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1029 invoked by uid 22784); 11 Jan 2002 01:30:13 -0000 From: Michael Snyder Newsgroups: cygnus.gdb Subject: Re: Changing the C/C++ compiler for gdb testsuite runs Date: Thu, 10 Jan 2002 17:30:00 -0000 Organization: Red Hat, Inc. Message-ID: <3C3E3E31.9B561351@redhat.com> References: <200201101345.NAA03946@cam-mail2.cambridge.arm.com> NNTP-Posting-Host: reddwarf.sfbay.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: cronkite.cygnus.com 1010712423 22914 205.180.231.12 (11 Jan 2002 01:27:03 GMT) X-Complaints-To: postmaster@cygnus.com NNTP-Posting-Date: 11 Jan 2002 01:27:03 GMT X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en To: gdb@sources.redhat.com DJ-Gateway: from newsgroup cygnus.gdb X-SW-Source: 2002-01/txt/msg00116.txt.bz2 Richard Earnshaw wrote: > > I'm not a dejagnu expert, so the answer to this may be obvious. > > 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.