[2626] in Kerberos_V5_Development
Re: RPC in libc?
daemon@ATHENA.MIT.EDU (Mark W. Eichin)
Wed Oct 22 14:30:45 1997
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
Cc: krbdev@MIT.EDU
From: eichin@MIT.EDU (Mark W. Eichin)
Date: 22 Oct 1997 14:20:17 -0400
In-Reply-To: Ken Hornstein's message of "Tue, 21 Oct 1997 11:26:31 -0400"
I did succeed in doing a full build for ppc-mklinux a long time back.
There *is* a trick to it, involving rpc... Basically the problem is
that you're getting part of the libc rpc, and part of the krb5 rpc.
When you get the collision, find out what is causing the dependency
and work back one step at a time (I did this by linking with a local
copy of libc, and using "ar d" to take out colliding .o files one at a
time.) Once you've found the common ancestor, add -ufunction-name to
the link command line; this forces the function to be resolved early,
ie. when the gssrpc lib is being processed, and pulls in the whole
chain, so that when whatever libc function needs it references it,
it's already linked in.
Regrettably, I don't remember what the function name was, and I don't
have a ppc-mklinux box to work with any more. If you want to give me
access to one, I could probably hunt it down...
