chris> If something includes kerberos/des.h, and then includes OpenSSL's
chris> des.h, there is a multiple definition collision of DES_KEY_SZ,
chris> des_ks_struct, bit_64, as well as des_key_schedule.
Uhmm, why should you include both des.h?
chris> Any ideas for fixes? My idea is to change the OpenSSL names,
chris> since I can't very likely expect people to patch Solaris.
A better idea would be to look in kerberos/des.h for some kind of
macro that is defined to mark that file as already included, and make
clever use of that macro. It works pretty often. Of course, there's
a chance there are other des.h with different macros, but I'd suggest
the same actions to deal with those as well...
BTW, you should check if the names that collide are objects that are
compatible. If not, some extra caution will prbably be needed, and it
again raises the question: why include both des.h?
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-161 43 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
