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: 29 May 2000 04:08:54 GMT Organization: Your Organization Lines: 37 Message-ID: <8gsqgm$k2u$2@bob.news.rcn.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Trace: Nxp2Mz6KjmqosCnlnUWGkpJtLVw+/z0A6XhxD4fK1Kg= X-Complaints-To: abuse AT rcn DOT com NNTP-Posting-Date: 29 May 2000 04:08:54 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 Sun, 28 May 2000 kknd_bl AT hotmail DOT com wrote: > >> every time I try to compile a program which includes netbd.h or >> sys/sockets.h or sys/types.h or netinet/in.h, djgpp gives a lot of >> error messages, like: >> >> 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 like the GCC compiler does so programs that contain networking code will run into problems. The solution to the problem is pretty simple. DJGPP should seriously consider adding/intergrating the WATT32 and libnet packages to the basic distrubtion. It'll be a win for everybody. DJGPP will be able to compile more programs, especially ones ported from linux, and the Watt32 and libnet authors will get more people testing/debugging their code.