Skip to content

Commit 36610f6

Browse files
committed
docs: document missing libcrypt.so.1 issue
Related to #113.
1 parent ae6b6b9 commit 36610f6

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

docs/quirks.rst

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -360,3 +360,27 @@ files included in the distributions. But there isn't a turnkey way to do this.
360360
And you can't easily remove ``_tkinter`` and its symbols from the pre-built
361361
and ready-to-use Python install included in this project's distribution
362362
artifacts.
363+
364+
.. _quirk_missing_libcrypt:
365+
366+
Missing ``libcrypt.so.1``
367+
=========================
368+
369+
Some Linux environments may complain about a missing ``libcrypt.so.1`` shared
370+
library dependency.
371+
372+
``libcrypt.so.1`` is mandated as part of the Linux Standard Base Core
373+
Specification and therefore should be present in Linux environments conforming
374+
to this specification. Most Linux distributions attempt to conform to this
375+
specification.
376+
377+
There was a time period when RedHat-maintained Linux distributions (Fedora,
378+
CentOS, RHEL) and their derivatives shipped a base OS environment that didn't
379+
include ``libcrypt.so.1``. See
380+
https://github.com/indygreg/python-build-standalone/issues/113 and
381+
https://bugzilla.redhat.com/show_bug.cgi?id=2055953 for more background. On
382+
these distributions, you can manually install the ``libxcrypt-compat`` package
383+
to provide the missing ``libcrypt.so.1`` library. Modern versions of these
384+
distros should install this package automatically when installing
385+
``redhat-lsb-core`` (or a similarly named) package. This package should be
386+
present in the base OS install.

0 commit comments

Comments
 (0)