Error while compiling krb 1.5

[Rainer.Heilke@atcoitek.com]

Not really intending to stick my nose in, but I think this may be interesting food to ponder...

No one has stated which version of what OS is involved here, other than Shivakeshav's comment about using Solaris, but it may be worthwhile reading this Sun blog entry about static linking going away starting with Solaris 10. Rod Evans has a good explanation of what is happening, and why:

http://blogs.sun.com/roller/page/rie?entry=static_linking_where_did_it

This, of course, doesn't address other OSes--or older versions of Solaris--directly, but I hope this is a worthwhile addition to the discussion.

Rainer Heilke

> -----Original Message-----
> From: krbdev-bounces at mit.edu [mailto:krbdev-bounces at mit.edu] 
> On Behalf Of Ken Hornstein
> Sent: Wednesday, July 05, 2006 9:10 AM
> To: krbdev at mit.edu
> Subject: Re: Error while compiling krb 1.5 
> 
> >That is something we'd like to clean up, though it hasn't been high  
> >on our priority list, because so far as we're aware it's not urgent  
> >for most other people either; we expect the most popular and most  
> >important use cases by far to involve deploying shared libraries  
> >only.  (We could be wrong.  But so far I think this is only the  
> >second complaint we've heard since putting out the pre-1.5 test  
> >releases.)
> 
> Have I complained yet?  I don't think I have, because I haven't been
> playing around with 1.5.  But anyway, I have a group of systems where
> static libraries are a requirement (basically because we have users
> download a precompiled set of binaries, and requiring the 
> users to have
> to somehow set up shared libraries would be a non-starter).
> 
> It does sound like it's a fixable problem, though.  Something 
> to keep in
> the back of my mind when I go to 1.5.
> 
> --Ken
> _______________________________________________
> krbdev mailing list             krbdev at mit.edu
> https://mailman.mit.edu/mailman/listinfo/krbdev
> 


The information transmitted is intended only for the addressee and may contain confidential, proprietary and/or privileged material. Any unauthorized review, distribution or other use of or the taking of any action in reliance upon this information is prohibited. If you receive this in error, please contact the sender and delete or destroy this message and any copies.