Sender: nate AT cartsys DOT com
Message-ID: <36DB190F.E2D57F1C@cartsys.com>
Date: Mon, 01 Mar 1999 14:47:43 -0800
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.1 i586)
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Integrating BSD socket networking into DJGPP
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990301112947 DOT 2578P-100000 AT is> <36DB0027 DOT FEBB1CCC AT meridian22 DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Richard Dawe wrote:
> 
> > >       I was wondering what the position is on integrating something
> > > like libsocket into DJGPP, in order to provide BSD socket networking.
> >
> > I'd vote for it, in general.
> >
> > But please tell more about the meaning of ``integrating''.  Is there
> > anything beyond providing a library against which DJGPP programs can
> > be linked?
> 
>         I was thinking of how to add it to the DJGPP source tree when I wrote the
> word "integrating". Naturally there's all the header files that need to be
> added, and the library, as you say.
> 
>         Unfortunately the library is 1 character too long to fit in 8+3 -
> libsocket.a. This will require some extra instructions. In libsocket there is
> a special target for renaming the library (& others) as appropriate. How would
> this be coped with in DJGPP?

Why?  DJGPP supports long file names when available, and when not the
names are simply truncated.  Even if the file is called `libsocke.a',
users can still do `-lsocket' as usual.

Whether DJ is OK with this is another question.  AFAIK djdev currently
has only 8+3 names.

>         Another question - is the DJGPP 2.02 in the v2/ directory actually the final
> release of 2.02, or is it a beta?

Final.  Betas have their own special subdirectory.
-- 

Nate Eldredge
nate AT cartsys DOT com