[1043] in Kerberos_V5_Development
Re: k5: sunos shared lib support
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Mon Apr 1 11:25:01 1996
Date: Mon, 1 Apr 96 11:25:42 EST
From: Barry Jaspan <bjaspan@MIT.EDU>
To: Richard Basch <basch@lehman.com>
Cc: krbdev@MIT.EDU
In-Reply-To: [1039]
Every -Ldir in the line is preserved in the runtime
path
We solved this problem at OV simply by linking all libraries as
explicit paths (relative for local libs, absolute for system libs).
It seems that autoconf would be pretty good generated such paths.
Will it be that difficult?
Incidentally, this is a problem even if you do not use shared krb5
libraries. Under SunOS for example, libc is shared, and all the -L
paths are searched for it. We had a customer who ran into some
problem because our /bin/login replacement was compiled this way. I
think one of our paths was pinging an NFS server of his, so when the
server was down he couldn't log in. Or something like that. The
short story is that you should NEVER EVER compile any program for
production use with -L, period. Always use explicit paths.
Barry
