This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: patch to add QNX NTO i386 support


   From: "Kris Warkentin" <kewarken@qnx.com>
   Cc: <ac131313@redhat.com>, <gdb-patches@sources.redhat.com>
   Date: Thu, 13 Feb 2003 17:29:13 -0500
   Content-Type: text/plain;
	   charset="iso-8859-1"
   X-Priority: 3
   X-MSMail-Priority: Normal
   X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

   >    From: "Kris Warkentin" <kewarken@qnx.com>
   >    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?

You can add to the various CONFIG_ variables, e.g. you would add
remote-nto.o to CONFIG_OBS.  See how the CLI, MI, TUI etc. are handled
in configure.in.

Anyway, I don't consider the fact that remote-nto.o is listed in
TDEPFILES a problem, as long as the *nto-tdep.c files don't depend on
it.

   > 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.

Huh?  Are you saying that, even though you don't mention tm-nto.h in
any of the Makefile-fragments you're adding, you need the file to
build GDB?

   I'm trying to solve a few annoying bugs (SOLIB_BKPT_NAME and
   SVR$_EXEC_EMU) first before I submit.

Fair enough.  I'm just looking forward to the end-result.

Mark


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]