Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Jim Blandy <jimb@red-bean.com>,
		sje@cup.hp.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove gdb/nlm subdirectory
Date: Mon, 27 Mar 2006 14:52:00 -0000	[thread overview]
Message-ID: <20060327042430.GA17549@nevyn.them.org> (raw)
In-Reply-To: <m3veu0ilea.fsf@gossamer.airs.com>

On Sun, Mar 26, 2006 at 08:03:57PM -0800, Ian Lance Taylor wrote:
> Daniel Jacobowitz <drow@false.org> writes:
> 
> > Well, in all the time I've been working on GDB, I've never seen a user
> > question about Netware, a GNATS PR about Netware, or a developer commit
> > tested on Netware.  To build it you need a Netware-provided SDK; I
> > don't know if those are still obtainable.
> 
> I'm in favor of removing it, but I just want to note that the last
> sentence is not correct.  You can build the gdb/nlm code using an
> i386-elf-gcc and nlmconv.  No non-GNU tools are required.

I was just going by this:

   This code is intended to produce an NLM (a NetWare Loadable Module)
   to run under Novell NetWare.  To create the NLM, compile this code
   into an object file using the NLM SDK on any i386 host,

If that's not true, where do you get these?

#ifdef __i386__
#include <dfs.h>
#include <conio.h>
#include <advanced.h>
#include <debugapi.h>
#include <process.h>
#else
#include <nwtypes.h>
#include <nwdfs.h>
#include <nwconio.h>
#include <nwadv.h>
#include <nwdbgapi.h>
#include <nwthread.h>
#endif

> However, it is true that the current sources won't build without
> modification.  The configure script looks for config/CPU/gdbserve.mt,
> and no such files exist.  The only two targets which ever worked were
> i386 and PPC, and the required gdbserve.mt files were removed with
> this change:
> 
> 2003-02-05  Andrew Cagney  <ac131313@redhat.com>
> 
> 	Remove orphaned hosts, targets and files.
>         ...
> 
> So since then it has been difficult to build the NLM debug server.  I
> think the lack of complaints about this is a compelling argument that
> the code is unused.

Ah - that's perfect, thank you.  That means the code has not built
since GDB 6.0.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-03-27  4:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24  3:27 Steve Ellcey
2006-03-24  8:31 ` Jim Blandy
2006-03-24  9:10   ` Daniel Jacobowitz
2006-03-24 20:21     ` Eli Zaretskii
2006-03-24 20:23       ` Daniel Jacobowitz
2006-03-24 20:30         ` Jim Blandy
2006-03-25 16:23           ` Eli Zaretskii
2006-03-25  0:04         ` Mark Kettenis
2006-03-25  6:57           ` Jim Blandy
2006-03-25 13:05             ` Eli Zaretskii
     [not found]               ` <20060328211848.GB10392@nevyn.them.org>
2006-03-28 22:18                 ` Daniel Jacobowitz
2006-03-29 15:58                   ` Eli Zaretskii
2006-03-27 13:25         ` Ian Lance Taylor
2006-03-27 14:52           ` Daniel Jacobowitz [this message]
2006-03-27 23:59             ` Ian Lance Taylor
2006-03-24 17:29 ` Eli Zaretskii
2006-03-29 23:40 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060327042430.GA17549@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ian@airs.com \
    --cc=jimb@red-bean.com \
    --cc=sje@cup.hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox