From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2033 invoked by alias); 7 Feb 2003 01:48:02 -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 2003 invoked from network); 7 Feb 2003 01:48:00 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 7 Feb 2003 01:48:00 -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 UAA20635; Thu, 6 Feb 2003 20:37:28 -0500 Received: from dash ([192.168.20.26]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id UAA19113; Thu, 6 Feb 2003 20:47:58 -0500 Message-ID: <008f01c2ce4b$427295f0$2a00a8c0@dash> From: "Kris Warkentin" To: "Andrew Cagney" Cc: References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <3E40387D.50001@redhat.com> Subject: Re: patch to add QNX NTO i386 support Date: Fri, 07 Feb 2003 01:48: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/msg00228.txt.bz2 > > * config/i386/nm-nto.h: New file > > The file nm-nto.h should not be needed. Instead define it's only macro > local to remote-nto.c. (Disclaimer, you're breaking new ground with > this one. Some existing targets don't have xm-*.h files, but I think > you're first with the no-*.h file). > > > * config/i386/nto.mh: New file > > Yes, you need this, you've a native support. When I got rid of nm-nto.h and took out 'NAT_FILE=nm-nto.h' from nto.mh, all of a sudden I wasn't building a native compiler anymore. Looks like configure uses the presence of a native file to determine whether to build a self hosted debugger or not. If I just 'touch nm-nto.h' and reconfigure, I build a native gdb. Any suggestions? I was thinking that I could perhaps point to one of my other headers and then share some remote and native definitions. As long as I'm asking questions, below is what I've reduced our tm-i386nto.h file to. Is it absolutely verboten to have this file? There are a few handy definitions there like EXTRA_GDBINIT and so on that we like to define per target. Also, I couldn't see how to get rid of the solib stuff. Is there some place else I can put these definitions? cheers, Kris #ifndef TM_I386QNX_H #define TM_I386QNX_H 1 /* Pick up most of what we need from the generic i386 target include file. */ #include "i386/tm-i386.h" #include "tm-qnxnto.h" #define __QNXTARGET__ #define QNX_TARGET_CPUTYPE CPUTYPE_X86 /* After a watchpoint trap, the PC points to the instruction after the one that caused the trap. Therefore we don't need to step over it. But we do need to reset the status register to avoid another trap. */ #define HAVE_CONTINUABLE_WATCHPOINT /* default processor for search path for libs */ #define SOLIB_PROCESSOR "x86" /* Use .ntox86-gdbinit */ #define EXTRA_GDBINIT_FILENAME ".ntox86-gdbinit" #define HANDLE_SVR4_EXEC_EMULATORS 1 #include "solib.h" /* shared lib support */ #endif /* ifndef TM_I386QNX_H */