From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12669 invoked by alias); 15 Jan 2002 18:24:50 -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 12630 invoked from network); 15 Jan 2002 18:24:50 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 15 Jan 2002 18:24:50 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16QYGP-0002Ge-00; Tue, 15 Jan 2002 13:24:49 -0500 Date: Tue, 15 Jan 2002 10:24:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Cc: Kevin Buettner , Michael Elizabeth Chastain , Richard.Earnshaw@arm.com Subject: Re: Changing the C/C++ compiler for gdb testsuite runs Message-ID: <20020115132449.A8635@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com, Kevin Buettner , Michael Elizabeth Chastain , Richard.Earnshaw@arm.com References: <200201101658.KAA16306@duracef.shout.net> <1020110190932.ZM5067@localhost.localdomain> <20020110143040.A9479@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020110143040.A9479@nevyn.them.org> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-01/txt/msg00164.txt.bz2 On Thu, Jan 10, 2002 at 02:30:40PM -0500, Daniel Jacobowitz wrote: > I do this by different board files. > > In dejagnu/baseboards, copy unix.exp. Edit it. It should originally > say: > > set_board_info compiler "[find_gcc]"; > > > I have: > set_board_info compiler "/opt/src/gcc/install-30/bin/gcc"; > set_board_info c++compiler "/opt/src/gcc/install-30/bin/g++"; > > There's matching variables for all the other compiler types (Java etc). > I don't yet test those. > > Then, to run: > ../../../src/dejagnu/runtest --target_board "unix unix3" blah.exp > > That will run tests for both the default GCC and the custom in > install-30. You can also do: > --target_board "unix/gdb:debug_flags=-gdwarf-2" > to test DWARF-2, or likewise for any other flag. There's a pure > /dwarf2 option but don't use it; that's dwarf-1 level 2. I've been > forgetting to file a DejaGNU bug report about this. > > The results of this thread should go in the GDB manual somewhere! As a followup, note that you can _NOT_ test multiple debug formats the way that GCC tests multilibs. You need to run with unix/gdb:debug_flags=-gdwarf-2, not just unix/-gdwarf-2. If you do the latter, most tests will be compiled with -g -gdwarf-2 (harmless), but nodebug.exp will be build with -gdwarf-2. Oops. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer