From: Ian Lance Taylor <ian@airs.com>
To: Daniel Jacobowitz <drow@false.org>
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 23:59:00 -0000 [thread overview]
Message-ID: <m3slp4gcsn.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20060327042430.GA17549@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> 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
Oh, you're right, sorry. You do need the NLM header files, and they
aren't in the GNU sources. They used to be available somewhere, but I
no longer remember where.
Ian
next prev parent reply other threads:[~2006-03-27 14:52 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
2006-03-27 23:59 ` Ian Lance Taylor [this message]
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=m3slp4gcsn.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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