This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: configure check for HAVE_CRYPT_R is wrong
Type: behavior Stage: patch review
Components: Versions: Python 3.11
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: christian.heimes
Priority: normal Keywords: patch

Created on 2021-11-15 15:41 by christian.heimes, last changed 2022-04-11 14:59 by admin.

Pull Requests
URL Status Linked Edit
PR 29563 closed christian.heimes, 2021-11-15 15:50
Messages (2)
msg406352 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2021-11-15 15:41
The configure check for HAVE_CRYPT_R assumes that all platforms have <crypt.h>. Some platforms like FreeBSD don't have <crypt.h> at all. Instead the crypt_r() prototype is defined in <unistd.h>.
msg406353 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2021-11-15 15:52

     Crypt Library (libcrypt, -lcrypt)

     #include <unistd.h>

     char *
     crypt(const char *key, const char *salt);
Date User Action Args
2022-04-11 14:59:52adminsetgithub: 89966
2021-11-15 15:52:50christian.heimessetmessages: + msg406353
2021-11-15 15:50:13christian.heimessetkeywords: + patch
stage: patch review
pull_requests: + pull_request27811
2021-11-15 15:41:05christian.heimescreate