Github messages for voidlinux
 help / color / mirror / Atom feed
From: Sheape <Sheape@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xbps-install -Su fails with "python3-3.12.0_1: broken, unresolvable shlib `libcrypt.so.1'"
Date: Sat, 30 Dec 2023 01:31:58 +0100	[thread overview]
Message-ID: <20231230003158.aAZnOhLth6ZkZrFyDc3sD4M8Om2ECfIitlbrvX7hdIo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47922@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

New comment by Sheape on void-packages repository

https://github.com/void-linux/void-packages/issues/47922#issuecomment-1872405922

Comment:
I get the same issue when compiling it from source using the template using the repo-ci.voidlinux.org mirror.
```
Error:  _crypt failed to import: /builddir/python3-3.12.0/build/lib.linux-x86_64-3.12/_crypt.cpython-312-x86_64-linux-gnu.so: undefined symbol: crypt
The necessary bits to build these optional modules were not found:
_tkinter              _uuid                 nis                
To find the necessary bits, look in configure.ac and config.log.

Following modules built successfully but were removed because they could not be imported:
_crypt
```

Im using void-buildroot-glibc:20230904R2 for the docker image

  parent reply	other threads:[~2023-12-30  0:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 10:38 [ISSUE] " michael-ball
2023-12-27 13:42 ` michael-ball
2023-12-27 14:09 ` classabbyamp
2023-12-27 14:09 ` classabbyamp
2023-12-27 16:10 ` michael-ball
2023-12-30  0:31 ` Sheape [this message]
2023-12-30  2:21 ` Sheape
2024-02-04  6:26 ` [ISSUE] [CLOSED] " ahesford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231230003158.aAZnOhLth6ZkZrFyDc3sD4M8Om2ECfIitlbrvX7hdIo@z \
    --to=sheape@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).