From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6138 invoked by alias); 12 Jan 2004 19:34:03 -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 6116 invoked from network); 12 Jan 2004 19:34:01 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 12 Jan 2004 19:34:01 -0000 Received: from redhat.com (toocool.toronto.redhat.com [172.16.14.72]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 705EE80006F; Mon, 12 Jan 2004 14:34:00 -0500 (EST) Message-ID: <4002F6A8.6000807@redhat.com> Date: Mon, 12 Jan 2004 19:34:00 -0000 From: "J. Johnston" Organization: Red Hat Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Andrew Cagney , gdb-patches@sources.redhat.com, binutils@sources.redhat.com, newlib@sources.redhat.com Subject: Re: [patch/rfc] Use i686-pc-linux-gnu as the releng target References: <4002C4DD.7040502@gnu.org> <20040112180911.GA20994@nevyn.them.org> In-Reply-To: <20040112180911.GA20994@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-01/txt/msg00322.txt.bz2 Daniel Jacobowitz wrote: > On Mon, Jan 12, 2004 at 11:01:33AM -0500, Andrew Cagney wrote: > >>Hello, >> >>GDB, and I suspect binutils, and just possibly newlib (true?), as part >>of the release process does: >> ./configure sun4 >>(it is so that the .info et.al. files can be generated). The problem is >>that GDB no longer configures for the good old sun4. >> >>This patch changes the system being used from "sun4" to "i686-pc-linux-gnu". >> >>For binutils, can the release engineer give this a wirl. > > > Works fine. > > >>For newlib, is this logic still used? Can that part of the file be removed? >> We don't use it for generating our snapshot releases. If you are building newlib on a native system, you have to specify --with-newlib in the configuration, otherwise, it normally doesn't get built. >>Once we've sorted things here I'll see about pushing this upstream into >>GCC repository (gcc doesn't use this file). > > > The GCC repository doesn't contain it, either. >