From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27415 invoked by alias); 6 Apr 2002 02:14:38 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27407 invoked from network); 6 Apr 2002 02:14:36 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 6 Apr 2002 02:14:36 -0000 Received: from redhat.com (notinuse.cygnus.com [205.180.231.12]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id SAA11843; Fri, 5 Apr 2002 18:13:50 -0800 (PST) Message-ID: <3CAE572C.95D08F17@redhat.com> Date: Fri, 05 Apr 2002 18:14:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Andrew Cagney CC: Daniel Jacobowitz , Elena Zannoni , gdb-patches@sources.redhat.com Subject: Re: [RFA/RFC] Multilibs and gdb.asm References: <15534.5336.562102.896601@localhost.redhat.com> <20020405164258.A30688@nevyn.them.org> <3CAE1C31.6090001@cygnus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00209.txt.bz2 Andrew Cagney wrote: > > > On Fri, Apr 05, 2002 at 04:19:20PM -0500, Elena Zannoni wrote: > > > >> > >> In gdb.asm/asm-source.exp, the testsuite passes multilib options to > >> the assembler according to the compiler syntax. > >> Obviously this doesn't work, as already noted by Nick Clifton in: > >> > >> http://sources.redhat.com/ml/gdb-patches/2002-01/msg00282.html > >> > >> A solution wasn't reached at the time. > >> > >> I found it useful to just bail out of the test if some multilibs were > >> detected. At least it reduced the noise in the testsuite results. > >> > >> Is this too drastic? > > > > > > I've got a silly suggestion. Is there any reason not to assemble by > > invoking the compiler, for this test? Let it do all the multilib > > footwork. > > What compiler? (There may be an assembler and linker but no compiler) No, Daniel's right. At some point last year, we changed the test so that it invokes "gdb_compile" to do the final link. I think that was because the compiler would figure out what libraries needed to be linked in. I've been vaguely worried about that change...