From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1259 invoked by alias); 13 Feb 2003 22:29:13 -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 1249 invoked from network); 13 Feb 2003 22:29:13 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 13 Feb 2003 22:29:13 -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 RAA09477; Thu, 13 Feb 2003 17:18:05 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id RAA17407; Thu, 13 Feb 2003 17:29:12 -0500 Message-ID: <021601c2d3af$562e07f0$0202040a@catdog> From: "Kris Warkentin" To: "Mark Kettenis" Cc: , References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <3E40387D.50001@redhat.com> <008f01c2ce4b$427295f0$2a00a8c0@dash> <86lm0r3nha.fsf@elgar.kettenis.dyndns.org> <01f301c2d2e4$afb31200$0202040a@catdog> <200302132220.h1DMKBxU000786@elgar.kettenis.dyndns.org> Subject: Re: patch to add QNX NTO i386 support Date: Thu, 13 Feb 2003 22:29: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/msg00314.txt.bz2 > From: "Kris Warkentin" > Date: Wed, 12 Feb 2003 17:18:35 -0500 > > 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. > > I think we'd want the remote stuff to be optional. One way to make it > such is having a configure option, say --enable-remote-nto, to enable > it (which would be the default on QNX NTO systems, where you'd be able > to use --disable-remote-nto to disable it). GDB should compile either > way (but the remote-nto stuff probably wouldn't be of any use except > for connecting to QNX NTO systems). How would this work? If the option were supplied would I append remote-qnx.o to TDEPFILES? > 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? > > Sorry I'm not following you here. There's no point in listing files > both in NATDEPFILES and TDEPFILES, since a native GDB by definition > also includes the target stuff for the host its being built for. Yes. Daniel J. explained this to me. > I'm missing config/tm-qnxnto.h from the files you listed. And what > purpose fulfills the tm-nto.h file you listed? Anyway, show me the > complete target-stuff and let's get that integrated first! The missing tm-qnxnto.h was an oversight - not necessary for the question I was asking. The tm-nto.h file is necessary because configure will not build a native debugger without it, even if it's empty. I'm trying to solve a few annoying bugs (SOLIB_BKPT_NAME and SVR$_EXEC_EMU) first before I submit. cheers, Kris