[krbdev.mit.edu #1793] alpha-osf ...

[Ken Raeburn via RT]

[subject truncated because RT is broken]

"Douglas E. Engert" <deengert at anl.gov> writes:
> This brings up a nit I have had with almost all packages that build 
> shared libs. They all assume that they can derived the -rpath from 
> the -L or they don't support -rpath. (or -R or what ever.)
> This is not always the case, and it may leave build directories in the
> -rpath which could be a security risk.  

Is this actually a problem with the MIT krb5 code?  I think we're
using -rpath/-R to specify the library install directory should be
used at run time, and not the build directory.  At least, if there's a
platform where we could do it and we're not, it's a bug.

Hm, I wonder how to best test that....  Shouldn't be too complicated,
we can probably even work it into a configure script or "make check"
or something.

Ken