Date: Sat, 2 Nov 1996 18:32:45 +0800 (GMT)
From: Orlando Andico <orly AT gibson DOT eee DOT upd DOT edu DOT ph>
To: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
cc: 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: <3275C517.2FBB@blackmagic.tait.co.nz>
Message-ID: <Pine.SGI.3.93.961102183116.7768A-100000@gibson.eee.upd.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 29 Oct 1996, Bill Currie wrote:

> Kai Ruottu wrote:
> > 
> > Orlando Andico <orly AT gibson DOT eee DOT upd DOT edu DOT ph> wrote:
> > 
> > >On the other hand, one thing which I sorely miss under DJGPP is sockets.
> > 
> >  There is a port of WATTCP for DJGPP - anybody tried this to make inet
> > applications?
> 
> Following the build instructions, I got it to ping successfully.
> 
> Bill
> 

Very good (kidding..)
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.