From: clee2 AT envirolink DOT org (Chris Lee) Newsgroups: comp.os.msdos.djgpp Subject: Re: netbd.h, sockets.h, in.h and types.h don't work Date: 30 May 2000 03:50:56 GMT Organization: Your Organization Lines: 50 Message-ID: <8gvdr0$a4i$2@bob.news.rcn.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Trace: eddUcINZsY7yGCViXwzFOWrrJ20UPE0QzaCajYz5MAk= X-Complaints-To: abuse AT rcn DOT com NNTP-Posting-Date: 30 May 2000 03:50:56 GMT X-No-Archive: Yes X-Newsreader: WinVN 0.99.10 beta8 [mds] (16bit) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com In article , eliz AT is DOT elta DOT co DOT il says... > > > >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. What do you need patches for? Just make sure that the various networking files the libraries use go into the proper directories. > >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. Look for dosppp06.zip on simtelnet.