Martin Mokrejs <[EMAIL PROTECTED]> added the comment:
Could it be the name clashing problem between -lcrypt and -lcrypto?
bash-3.00# ar x /usr/lib/libcrypt.a;nm -g des_crypt.o
U ___errno
0000033c T _des_crypt
00000274 T _des_encrypt
U _des_encrypt1
000001b0 T _des_setkey
U _mutex_lock
U _mutex_unlock
U _thr_getspecific
U _thr_keycreate
U _thr_setspecific
0000033c W des_crypt
00000274 W des_encrypt
000001b0 W des_setkey
U free
U malloc
bash-3.00# ar x /usr/local/lib/libcrypto.a;nm -g des_crypt.o
U ___errno
0000033c T _des_crypt
00000274 T _des_encrypt
U _des_encrypt1
000001b0 T _des_setkey
U _mutex_lock
U _mutex_unlock
U _thr_getspecific
U _thr_keycreate
U _thr_setspecific
0000033c W des_crypt
00000274 W des_encrypt
000001b0 W des_setkey
U free
U malloc
bash-3.00#
There used to be name clashes between -lcrypt from KTH-KRB/HEIMDAL
with those from openssl -lcrypto in the past. I think that was
"fixed" around/in openssl-2.7 and heimdal-1.0. The clashes caused
openssh dying when compiled with kerberos4 support because the
functions of same names expected in some way different data.
I am sure you would Goggle it out.
_______________________________________
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3264>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
