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:31:57 GMT Organization: Your Organization Lines: 40 Message-ID: <8gvcnd$a4i$1@bob.news.rcn.net> References: <8gsqgm$k2u$2 AT bob DOT news DOT rcn DOT net> <3932E1A8 DOT 8BD99916 AT bigfoot DOT com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Trace: p+eZP5jassSYkWoHCvEe2Dz5x9gy7zGHMjN4IUistNc= X-Complaints-To: abuse AT rcn DOT com NNTP-Posting-Date: 30 May 2000 03:31:57 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 <3932E1A8 DOT 8BD99916 AT bigfoot DOT com>, richdawe AT bigfoot DOT com says... > > >Hello. > >Chris Lee wrote: >> The solution to the problem is pretty simple. DJGPP should seriously >> consider adding/intergrating the WATT32 and libnet packages to the basic >> distrubtion. > >The addition of a networking library to DJGPP would probably add a lot of >code to libc. If most people don't use networking, is it worth it? Ask the people who compile software like trn,pine,lynx,kermit ect,ect,ect under linux using GCC. And just how would including/intergrating a networking library like yours or Watt32 into DJGPP add any code whatsoever to libc? All that would really happening is making sure that the DJGPP version of Watt32 and other various BSD-compat networking libs for DJGPP have been properly configured to make sure they work with DJGPP out of the box so to speak when compiling programs that call/look for things like netbd.h, sockets.h, in.h and types.h.