From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19021 invoked by alias); 25 Nov 2002 21:17:57 -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 18960 invoked from network); 25 Nov 2002 21:17:55 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 25 Nov 2002 21:17:55 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 054DD3E66 for ; Mon, 25 Nov 2002 16:17:52 -0500 (EST) Message-ID: <3DE2937F.4010007@redhat.com> Date: Mon, 25 Nov 2002 13:17:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Always multi-arch the SPARC, dump sparclet? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00359.txt.bz2 Hello, The SPARC target has a number of variants that don't yet build with multi-arch enabled (e.g., sparc-elf). I'd like to propose that the switch simply be thrown and any non-multi-arch code be ripped out. Acceptance criteria for such a change being simply `it still builds'. This shouldn't affect things like GNU/Linux, which, I believe, do already build with multi-arch enabled. This will, however, affect non-nulti-arch SPARC targets such as the sparclet potentially leading to breakage. Thoughts? Andrew