Date: Sun, 3 Nov 1996 11:17:05 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Orlando Andico <orly AT gibson DOT eee DOT upd DOT edu DOT ph>
Cc: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>,
        Kai Ruottu <karuottu AT freenet DOT hut DOT fi>, djgpp AT delorie DOT com
Subject: Re: Sockets under DJGPP (was: need advice on djgpp vs. Turbo C)
In-Reply-To: <Pine.SGI.3.93.961102183116.7768A-100000@gibson.eee.upd.edu.ph>
Message-Id: <Pine.SUN.3.91.961103111246.27986H-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sat, 2 Nov 1996, Orlando Andico wrote:

> > Following the build instructions, I got it to ping successfully.
> 
> The ping program is apparently a trivial sort. I got it to build under
> both DJGPP 1.x and 2.0, and it pinged, yes, but according to the porter it
> can't do blocking I/O. So I tried using select() to poll the port and
> avoid use of blocking I/O, but that did not work. The level of support is
> definitely NOT at the level where you can recompile your simple Unix
> network apps under DJGPP, unfortunately.

Without looking at the sources, I'd guess that since the port was done 
for DJGPP v1.x, it doesn't use the filesystem extensions feature 
introduced with v2.0.  I suggest to whoever is interested to check out 
the filesystem extensions and implement TCP/IP support on that level.  If 
you do this, all the rest of I/O (including `select') is taken care of 
automagically for you.  It's an incredible tool for extending DJGPP, 
believe me.  (Thank you, DJ, for including it!)