From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19954 invoked by alias); 10 Sep 2008 18:01:23 -0000 Received: (qmail 19863 invoked by uid 22791); 10 Sep 2008 18:01:21 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 10 Sep 2008 18:00:37 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 086CB2A96A4; Wed, 10 Sep 2008 14:00:35 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3rCkuqNYTsQK; Wed, 10 Sep 2008 14:00:34 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 065092A96A2; Wed, 10 Sep 2008 14:00:34 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id CFEB2E7ACD; Wed, 10 Sep 2008 20:00:18 +0200 (CEST) Date: Wed, 10 Sep 2008 18:01:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [autodeps] gnu-nat, autogenerated files Message-ID: <20080910180018.GP12222@adacore.com> References: <200809091606.45512.pedro@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200809091606.45512.pedro@codesourcery.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-09/txt/msg00218.txt.bz2 > 2008-09-09 Pedro Alves > > * Makefile.in (generated_files): Add $(host_generated_files). > * config/i386/i386gnu.mh (host_generated_files): New. This one is a little beyond my knowledge of Makefile, particularly since the build system has changed recently. The idea seems right to me (adding a new variable in the mh file). But I'm still wondering whether it would be possible to use the NAT_FILE to include the list of generated files. Tom, what do you think? Probably be a little hacky... If we introduce a new variable, I propose that its name be capitalized, like most (if not all) variables we have been using so far. I like HOST_GENERATED_FILES as you suggested. We also need to document this new variable in gdbint. Perhaps around there: @table @file @vindex NATDEPFILES @item gdb/config/@var{arch}/@var{xyz}.mh Specifies Makefile fragments needed by a @emph{native} configuration on machine @var{xyz}. In particular, this lists the required native-dependent object files, by defining @samp{NATDEPFILES=@dots{}}. Also specifies the header file which describes native support on @var{xyz}, by defining @samp{NAT_FILE= nm-@var{xyz}.h}. You can also define @samp{NAT_CFLAGS}, @samp{NAT_ADD_FILES}, @samp{NAT_CLIBS}, @samp{NAT_CDEPS}, etc.; see @file{Makefile.in}. @emph{Maintainer's note: The @file{.mh} suffix is because this file originally contained @file{Makefile} fragments for hosting @value{GDBN} on machine @var{xyz}. While the file is no longer used for this purpose, the @file{.mh} suffix remains. Perhaps someone will eventually rename these fragments so that they have a @file{.mn} suffix.} GMs, Tom, help! -- Joel