From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14478 invoked by alias); 9 Sep 2008 16:09:41 -0000 Received: (qmail 14467 invoked by uid 22791); 9 Sep 2008 16:09:40 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 09 Sep 2008 16:09:06 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id m89G3VWb017305; Tue, 9 Sep 2008 12:03:52 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m89G3K8j023045; Tue, 9 Sep 2008 12:03:20 -0400 Received: from opsy.redhat.com (vpn-10-127.bos.redhat.com [10.16.10.127]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id m89G3JBK007776; Tue, 9 Sep 2008 12:03:19 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id A223E3785D7; Tue, 9 Sep 2008 10:03:14 -0600 (MDT) To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [autodeps] gnu-nat, autogenerated files References: <200809091606.45512.pedro@codesourcery.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Tue, 09 Sep 2008 16:09:00 -0000 In-Reply-To: <200809091606.45512.pedro@codesourcery.com> (Pedro Alves's message of "Tue\, 9 Sep 2008 16\:06\:45 +0100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00187.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> These are generated headers, built from the corresponding .defs files in Pedro> the tree. Their build rules are in config/i386/i386gnu.mh. Pedro> Is this the right approach? Yes. I didn't know about the .mh files, sorry about that. I read through them all just now and I noticed that they inconsistently use NAT_FILE. Some use config/ and some do not, e.g.: config/pa/linux.mh:NAT_FILE= config/nm-linux.h config/alpha/alpha-osf3.mh:NAT_FILE= nm-osf3.h AFAICT this variable is only used for the TAGS rule. So, maybe it doesn't matter much. Or maybe it could just be deleted. Tom