Date: Mon, 29 May 2000 10:21:48 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Chris Lee <clee2 AT envirolink DOT org>
cc: djgpp AT delorie DOT com
Subject: Re: netbd.h, sockets.h, in.h and types.h don't work
In-Reply-To: <8gsqgm$k2u$2@bob.news.rcn.net>
Message-ID: <Pine.SUN.3.91.1000529101954.24119G-100000-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 29 May 2000, Chris Lee wrote:

> >> c:/djgpp/include/sys/socket.h error: windows.h, no such file or
> >> directory
> >
> >See section 8.2 of the DJGPP FAQ.  In a nutshell, these programs either 
> >need add-on packages or do not support DJGPP at all.
> 
> The answer to the question in *ENGLISH* is that DJGPP doesn't have a TCP/IP 
> stack or networking libs

I thought I was telling the same thing, and also in English.

> like the GCC compiler does

Hmm?  GCC does not include any networking libraries in its
distribution.  In fact, it doesn't include *any* libraries at all,
except the tiny libgcc.a that emulates some missing instructions on
specific platforms.

> The solution to the problem is pretty simple. DJGPP should seriously 
> consider adding/intergrating the WATT32 and libnet packages to the basic 
> distrubtion.

Patches to make this happen are most welcome.

Note that, to have TCP/IP on DOS, you will typically need a device
driver or a TSR for whatever hardware you use to access the physical
layer.