From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17522 invoked by alias); 11 Jan 2002 10:23:58 -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 17487 invoked from network); 11 Jan 2002 10:23:56 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 11 Jan 2002 10:23:56 -0000 Received: by fw-cam.cambridge.arm.com; id KAA29585; Fri, 11 Jan 2002 10:23:54 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma029189; Fri, 11 Jan 02 10:23:29 GMT Received: from cam-mail2.cambridge.arm.com (localhost [127.0.0.1]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id KAA13957; Fri, 11 Jan 2002 10:23:29 GMT Received: from sun18.cambridge.arm.com (sun18.cambridge.arm.com [172.16.2.18]) by cam-mail2.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id KAA26358; Fri, 11 Jan 2002 10:23:28 GMT Message-Id: <200201111023.KAA26358@cam-mail2.cambridge.arm.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Snyder cc: gdb@sources.redhat.com, Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. X-Url: http://www.arm.com/ Subject: Re: Changing the C/C++ compiler for gdb testsuite runs In-reply-to: Your message of "Thu, 10 Jan 2002 17:21:53 PST." <3C3E3E31.9B561351@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Jan 2002 02:23:00 -0000 From: Richard Earnshaw X-SW-Source: 2002-01/txt/msg00122.txt.bz2 > > 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. R.