Re: patch to add QNX NTO i386 support

["Kris Warkentin" <kewarken@qnx.com>]

> 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