Sender:	root AT delorie DOT com
Message-ID:	<3922B36A.18BB8874@inti.gov.ar>
Date:	Wed, 17 May 2000 11:57:46 -0300
From:	salvador <salvador AT inti DOT gov DOT ar>
Organization:	INTI
X-Mailer:	Mozilla 4.72 [en] (X11; U; Linux 2.0.38 i686)
X-Accept-Language:	es-AR, en, es
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
Subject:	Re: Sun RPC for djgpp?
References:	<39201D5E DOT 595121FB AT inti DOT gov DOT ar> <39203E55 DOT F221A9C8 AT bigfoot DOT com> <392188E3 DOT 1D56D2F0 AT inti DOT gov DOT ar> <3921AFB9 DOT FD71F12 AT bigfoot DOT com>
Reply-To:	djgpp AT delorie DOT com

Richard Dawe wrote:

> > Gisle Vanem ported the client stuff to WATTCP. It uses packetdrivers and
> > I'll run the client in Win9x boxes so I don't think I'll be able to use
> > it.
>
> You can get an NDIS-to-packet driver shim, called NDISPKT (I think). I
> tried this once, but I couldn't get it to work. Gisle Vanem has mentioned
> it on the Watt-32 mailing list, so I guess it works and I just have no
> idea how to set it up properly. ;)

Gisle sent me a link, I'll test it as soon as I can.

> > BTW: libsocket seems to define some RPC structure in the headers, why? I
> > think it makes collisions with some RPC header.
>
> Good question. I think they were there when I took over maintainership of
> libsocket. Which RPC structures do you mean? I can remove them for
> libsocket 0.7.4 beta 4.

I think that's rpcent, it makes collisions with some rpc header.
I saw it when I did a silly test to see if I could compile the wattcp code
using libsocket ;-)

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
                    set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013

- Raw text -