[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Change by Maxim Barabanov : -- pull_requests: +5126 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin Mokrejs <[EMAIL PROTECTED]> added the comment: Confirming the enabling line 216 like below helped. Thanks. Maybe change "Resolution"? 204 # Socket module helper for SSL support; you must comment out the other 205 # socket line above, and possibly edit the SSL variable: 206 #SS

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Ah, ok. I completely missed the point of the error message (i.e. "relocations remain"), and misinterpreted it as missing symbols. So I still recommend doing what I recommended back then: Uncomment the line in Modules/Setup to build the crypt

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin Mokrejs <[EMAIL PROTECTED]> added the comment: You say "did always work"? http://mail.python.org/pipermail/python-list/2002-December/177479.html Maybe the reason why in ruby they forced to -shared flag because it was possible to link only with the shared library? I do not know from which

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: No. We are not linking with libcrypto at all, so there can't be clashes. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

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 033c T _des_crypt 0274 T _des_encrypt U _des_encrypt1 01b0 T _des_setkey

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Ok. I have no further ideas on what the problem might be, but I'm confident that linking with a different library is not the right thing to do. Linking with -lcrypt did always work on Solaris 2.6, so I'm not going to change that. --

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin Mokrejs <[EMAIL PROTECTED]> added the comment: # ar x /usr/lib/libcrypt.a;nm -g des_crypt.o U ___errno 033c T _des_crypt 0274 T _des_encrypt U _des_encrypt1 01b0 T _des_setkey U _mutex_lock U _mutex_unlock U _thr_getspecific

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Something must be broken with your system installation. des_crypt.o should define the function _des_crypt (ar x /usr/lib/libcrypt.a;nm -g des_crypt.o). What linker are you using? It seems that the shared version of libcrypt was only added in

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin Mokrejs <[EMAIL PROTECTED]> added the comment: # ar tv /usr/lib/libcrypt.a rw-rw-r-- 0/1 1296 Jul 16 05:57 1997 crypt.o rw-rw-r-- 0/1 4996 Jul 16 05:57 1997 cryptio.o rw-rw-r-- 0/1 1508 Jul 16 05:57 1997 des_encrypt.o rw-rw-r-- 0/1 5356 Jul 16 05:58 1997 des_crypt.o # ls -la /usr/l

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Why didn't it link with /usr/lib/libcrypt.so? That has always worked on Solaris, including Solaris 2.6. In addition, even if it did decide to use libcrypt.a for some strange reason, it should still link successfully, since libcrypt.a should

[issue3264] Use -lcrypto instead of -lcrypt on Solaris 2.6 when available

New submission from Martin Mokrejs <[EMAIL PROTECTED]>: Hi, although the issues libraries to be created with -fpic are known I still do believe ./config could do something here: building 'crypt' extension gcc -shared -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes build/