From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22556 invoked by alias); 9 Sep 2008 16:18:37 -0000 Received: (qmail 22544 invoked by uid 22791); 9 Sep 2008 16:18:36 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 09 Sep 2008 16:17:57 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 516581018E; Tue, 9 Sep 2008 16:17:55 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 3405610140; Tue, 9 Sep 2008 16:17:55 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Kd5uc-0007gU-5k; Tue, 09 Sep 2008 12:17:54 -0400 Date: Tue, 09 Sep 2008 16:18:00 -0000 From: Daniel Jacobowitz To: Tom Tromey Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: [autodeps] gnu-nat, autogenerated files Message-ID: <20080909161754.GA29292@caradoc.them.org> Mail-Followup-To: Tom Tromey , Pedro Alves , gdb-patches@sourceware.org References: <200809091606.45512.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes 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/msg00188.txt.bz2 On Tue, Sep 09, 2008 at 10:03:13AM -0600, Tom Tromey wrote: > >>>>> "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. No, search for NAT_FILE in configure.ac. This file is included as nm.h in native GDBs; it's where native target configuration used to live, and the remaining ones are still used. Also: case "${nativefile}" in nm-*.h ) GDB_NM_FILE="config/${gdb_host_cpu}/${nativefile}" ;; * ) GDB_NM_FILE="${nativefile}" esac -- Daniel Jacobowitz CodeSourcery