From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28486 invoked by alias); 13 Feb 2003 22:21:24 -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 28476 invoked from network); 13 Feb 2003 22:21:23 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (62.163.169.212) by 172.16.49.205 with SMTP; 13 Feb 2003 22:21:23 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6/8.12.5) with ESMTP id h1DMKRRs000397; Thu, 13 Feb 2003 23:20:27 +0100 (CET) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6/8.12.6) with ESMTP id h1DMKBYd000789; Thu, 13 Feb 2003 23:20:11 +0100 (CET) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6/8.12.6/Submit) id h1DMKBxU000786; Thu, 13 Feb 2003 23:20:11 +0100 (CET) Date: Thu, 13 Feb 2003 22:21:00 -0000 Message-Id: <200302132220.h1DMKBxU000786@elgar.kettenis.dyndns.org> From: Mark Kettenis To: kewarken@qnx.com CC: ac131313@redhat.com, gdb-patches@sources.redhat.com In-reply-to: <01f301c2d2e4$afb31200$0202040a@catdog> (kewarken@qnx.com) Subject: Re: patch to add QNX NTO i386 support References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <3E40387D.50001@redhat.com> <008f01c2ce4b$427295f0$2a00a8c0@dash> <86lm0r3nha.fsf@elgar.kettenis.dyndns.org> <01f301c2d2e4$afb31200$0202040a@catdog> X-SW-Source: 2003-02/txt/msg00312.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). 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. 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! Mark