[2617] in Kerberos_V5_Development
Re: RPC in libc?
daemon@ATHENA.MIT.EDU (lukeh@xedoc.com)
Tue Oct 21 22:37:54 1997
From: <lukeh@xedoc.com>
Date: Wed, 22 Oct 97 12:37:02 +1000
To: assar@sics.se
Cc: tlyu@MIT.EDU, kenh@cmf.nrl.navy.mil, dima@best.net, krbdev@MIT.EDU
You wrote:
>From: Assar Westerlund <assar@sics.se>
>Subject: Re: RPC in libc?
>To: Tom Yu <tlyu@MIT.EDU>
>Cc: Ken Hornstein <kenh@cmf.nrl.navy.mil>, dima@best.net, krbdev@MIT.EDU
>Date: 22 Oct 1997 03:49:47 +0200
>
>Tom Yu <tlyu@MIT.EDU> writes:
>> Even better, scrap GSSRPC completely and re-write it.
>
>The protocol and/or the implementation? And outside the US, I
>guess. :-)
And one that supports RPCSEC_GSS (RFC 2203) :-)
WRT the initial poster's problem: most linkers have a flag to allow multiply
defined symbols, although this is a bad thing.
eg, under NEXTSTEP:
-m Don't treat multiply defined symbols as a hard error;
instead, simply print a warning. The first such symbol
is used for linking; its value is used for the symbol
in the symbol table. The other symbols by the same
name may be used in the resulting output file through
local references. This can still produce a resulting
output file that is in error. This flag's use is
strongly discouraged!
-- Luke
