From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20078 invoked by alias); 24 Jan 2003 19:16:27 -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 20065 invoked from network); 24 Jan 2003 19:16:27 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 24 Jan 2003 19:16:27 -0000 Received: from free.redhat.lsd.ic.unicamp.br (aoliva.cipe.redhat.com [10.0.1.10]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id h0OJGLg31223; Fri, 24 Jan 2003 14:16:21 -0500 Received: from free.redhat.lsd.ic.unicamp.br (localhost.localdomain [127.0.0.1]) by free.redhat.lsd.ic.unicamp.br (8.12.7/8.12.7) with ESMTP id h0OJGLMr009785; Fri, 24 Jan 2003 17:16:21 -0200 Received: (from aoliva@localhost) by free.redhat.lsd.ic.unicamp.br (8.12.7/8.12.7/Submit) id h0OJGIT5009781; Fri, 24 Jan 2003 17:16:18 -0200 To: Nathanael Nerode Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, binutils@sources.redhat.com Subject: Re: (toplevel patch) Use canonical names for target_subdir, build_subdir. References: <20030124034053.GA22615@doctormoo> <3E3186B3.2050906@twcny.rr.com> From: Alexandre Oliva Organization: GCC Team, Red Hat Date: Fri, 24 Jan 2003 19:16:00 -0000 In-Reply-To: <3E3186B3.2050906@twcny.rr.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-01/txt/msg00719.txt.bz2 On Jan 24, 2003, Nathanael Nerode wrote: >> I see where you're coming from, but we're really going to have to bite >> the bullet and duplicate autoconf 2.5x's behavior WRT machine name > You mean autoconf 2.13's behavior, I assume... No, I meant duplicating the logic that 2.5x uses to set canonical names to propagate the corresponding non-canonical names. > OK. I'll do this the easy way: I'll write Autoconf macros which > determine the "target_subdir" and "build_subdir" (exactly the same way > they're determined now), put the macros in an include file, and > rewrite the configure scripts to include it. How does that sound? I fail to see the point, but if you want to take the code out into a macro, don't let me stop you. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer