Date: Thu, 1 Jun 2000 08:53:14 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: netbd.h, sockets.h, in.h and types.h don't work
In-Reply-To: <8h41gc$o7b$1@bob.news.rcn.net>
Message-ID: <Pine.SUN.3.91.1000601085256.17554C@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 31 May 2000, Chris Lee wrote:

> >> Ask the people who compile software like trn,pine,lynx,kermit ect,ect,ect 
> >> under linux using GCC.
> >
> >Asking those people is bound to bring a very biased answer.  Rich was 
> >talking about DJGPP users, not about Linux users.
> 
> Err it's basically linux users who are using DJGPP to port Lynx to 
> windows and dos, so they are DJGPP users right?

I don't know.  Your original message said nothing about porting, it
just mentioned compiling under Linux.  Most people who port packages
to DJGPP don't work on Linux, AFAIK.

> >> And just how would including/intergrating a networking library like 
> >> yours or Watt32 into DJGPP add any code whatsoever to libc? 
> >
> >Obviously, the size of libc.a gets larger.  So it takes longer to
> >download djdevNNN.zip.
> 
> Dude we're NOT talking about Microsoft-style intergration here.....

Sorry, I cannot parse this.  Don't you agree that the development
environment will become larger?  And what's Microsoft got to do with
this?