From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4265 invoked by alias); 12 Feb 2003 22:44:42 -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 4258 invoked from network); 12 Feb 2003 22:44:42 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 12 Feb 2003 22:44:42 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18j7VW-0004in-00 for ; Wed, 12 Feb 2003 18:45:42 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18j5cN-0000mD-00 for ; Wed, 12 Feb 2003 17:44:39 -0500 Date: Wed, 12 Feb 2003 22:44:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Subject: Re: patch to add QNX NTO i386 support Message-ID: <20030212224439.GA2968@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <3E40387D.50001@redhat.com> <008f01c2ce4b$427295f0$2a00a8c0@dash> <86lm0r3nha.fsf@elgar.kettenis.dyndns.org> <01f301c2d2e4$afb31200$0202040a@catdog> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01f301c2d2e4$afb31200$0202040a@catdog> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-02/txt/msg00297.txt.bz2 On Wed, Feb 12, 2003 at 05:18:35PM -0500, Kris Warkentin wrote: > Okay. I've got all our config files down to what's below. Not much left to > them. Andrew had wanted me to submit separate native and remote patches but > I can't figure out how to do that. We would never build a native only gdb - > we always support the remote protocol as well - so I'm at a loss for how to > get it to NOT compile the remote-nto.c file. You don't; basically, it means you submit the remote part first and then the native part. > As you can see, I've got the common stuff separated into nto-tdep.c and > i386-nto-tdep.c which will be used by both remote-nto.c and nto-procfs.c. > The problem seems to be that when I build a native debugger, it includes the > stuff from i386nto.mt as well. I'm thinking that I want NATDEPFILES and > TDEPFILES to both have the *nto-tdep in them but then where does the > remote-nto.c go? Any help? A native build should include both NATDEPFILES and TDEPFILES; is it not doing that? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer