From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13855 invoked by alias); 13 Feb 2003 00:52:48 -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 13709 invoked from network); 13 Feb 2003 00:52:48 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 13 Feb 2003 00:52:48 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id TAA21273; Wed, 12 Feb 2003 19:41:44 -0500 Received: from dash ([192.168.20.30]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id TAA31177; Wed, 12 Feb 2003 19:52:46 -0500 Message-ID: <00b101c2d2fa$b066a890$2a00a8c0@dash> From: "Kris Warkentin" To: "Daniel Jacobowitz" , References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <3E40387D.50001@redhat.com> <008f01c2ce4b$427295f0$2a00a8c0@dash> <86lm0r3nha.fsf@elgar.kettenis.dyndns.org> <01f301c2d2e4$afb31200$0202040a@catdog> <20030212224439.GA2968@nevyn.them.org> Subject: Re: patch to add QNX NTO i386 support Date: Thu, 13 Feb 2003 00:52:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-02/txt/msg00298.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. Okay. Maybe I got the order mixed up. > > 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? Yes it does. That was what was confusing me. If I'm submitting the remote part first, then I'm no longer confused. The difference between remote and native is only one file either way. Either compile nto-procfs.c or remote-nto.c. Thanks Daniel. cheers, Kris