From: Richard Dawe Newsgroups: comp.os.msdos.djgpp Subject: Re: netbd.h, sockets.h, in.h and types.h don't work Date: Tue, 30 May 2000 20:13:14 +0100 Organization: Customer of Planet Online Lines: 48 Message-ID: <393412CA.56078E0F@bigfoot.com> References: <8gsqgm$k2u$2 AT bob DOT news DOT rcn DOT net> <3932E1A8 DOT 8BD99916 AT bigfoot DOT com> <8gvcnd$a4i$1 AT bob DOT news DOT rcn DOT net> NNTP-Posting-Host: modem-157.chlorine.dialup.pol.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: newsg1.svr.pol.co.uk 959716351 5977 62.136.16.157 (30 May 2000 19:52:31 GMT) NNTP-Posting-Date: 30 May 2000 19:52:31 GMT X-Complaints-To: abuse AT theplanet DOT net X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586) X-Accept-Language: de,fr To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hello. Chris Lee wrote: > > Richard Dawe wrote: > > 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? [snip] > And just how would including/intergrating a networking library like > yours or Watt32 into DJGPP add any code whatsoever to libc? OK, point taken it would actually be in libsocket.a (libsocke.a on DOS), but if it's part of DJGPP, then it would increase the size of the djdev ZIP file, unnecessarily for most people IMHO. > 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. Well, that's the plan with libsocket at the moment. If this doesn't happen, please tell me what I need to do to get it to happen. Hopefully the latest release will be better in many ways. I dumped man pages and switched to info docs, eliminating most of the hassle with long vs. short filenames. I'm also working on the integration aspect and making it easier for users and their program users to configure. Watt-32 built pretty simply from sources last time I tried. I don't know about the binary release, though. Perhaps part of the problem is that some of the header files already exist in DJGPP - netinet/in.h is one case. Also, some defines may need to be added to header files - e.g. S_IFSOCK, S_ISSOCK. I think the problem is then how to add basic networking functionality to DJGPP, to aid integration of network libs, without misleading configure scripts, etc. into thinking that vanilla DJGPP has networking facilities. I mean, a configure script may assume lots of things if S_ISSOCK is defined. I have to admit I thought you meant actual code integration into DJGPP, rather than making DJGPP + networking lib work together easily. The latter is something I've thought about a lot. Bye, -- Richard Dawe richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/