This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: CVS using a proxy ?
- To: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Subject: Re: CVS using a proxy ?
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Sat, 18 Jul 1998 19:07:31 +0100
- Cc: Eric NICOLAS <nicolas at bnp-eng dot remcomp dot com>, egcs at cygnus dot com, kingdon at cyclic dot com, larry dot jones at sdrc dot com
- Cc: rearnsha at sun52 dot arm dot com
- Organization: ARM Ltd.
- Reply-To: richard dot earnshaw at arm dot com
hans-peter.nilsson@axis.com said:
> ** You don't need to patch cvs at all: just add "-lsocks5_sh" to the
> LIBS ** variable (like in "make LIBS=-lsocks5_sh") when you make the
> cvs client.
> (To the CVS developers mentioned on the socks-related cvs devel pages
> --
> no, I'm not on devel-cvs@cyclic.com:
> Maybe the presence of socks could be detected with an autoconf
> rule,
> supported by a --with-socks to configure? It's not on your
> (cvs)web.)
I have a similar environment. But there is no need to use a special
(socksified) variant of cvs. For machines that support dynamic linking
there is a script that comes with socks that allows you to change the inet
protocol stack used at run time. In effect, you can make cvs talk to a
socks server by typing
runsocks cvs ...
See the documentation that comes with the socks libraries.
Richard.