From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1555 invoked by alias); 10 Jan 2002 16:58:09 -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 1526 invoked from network); 10 Jan 2002 16:58:05 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 10 Jan 2002 16:58:05 -0000 Received: (from mec@localhost) by duracef.shout.net (8.8.7/8.8.7) id KAA16306; Thu, 10 Jan 2002 10:58:05 -0600 Date: Thu, 10 Jan 2002 08:58:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200201101658.KAA16306@duracef.shout.net> To: Richard.Earnshaw@arm.com Subject: Re: Changing the C/C++ compiler for gdb testsuite runs Cc: gdb@sources.redhat.com X-SW-Source: 2002-01/txt/msg00090.txt.bz2 Richard Earnshaw writes: > 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 build my compilers with "prefix=/blah/blah/2002-01-10/blah ...." and then I go ahead and install the compiler. When I run the gdb test suite, I set $PATH to the place where the compiler-under-test lives. You may need to set $LD_LIBRARY_PATH as well if you build gcc with shared libraries (libgcc and libstdc++). If you build gcc and gdb in a unified build tree then dejagnu will find and use the uninstalled compiler in the unified build tree, even in preference to $PATH. That behaviour actually got in my way so I stopped using unified trees. Michael C