unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Athena Martin via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 64309@debbugs.gnu.org
Subject: bug#64309: Python dlopen()s musl libc
Date: Mon, 26 Jun 2023 20:42:30 -0400	[thread overview]
Message-ID: <20230626204230.7b3b773a@spock.hosts.alm.website> (raw)

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

I've had experiences now with multiple Guix packages, including gajim
(bug 60235) and now python-neovim-remote, which have an issue where
Python tries to dlopen() libc, but finds the system libc instead of
Guix's, resulting on Alpine Linux hosts in a crash with this message:

ImportError: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory

There are a variety of tracebacks that lead up to this, depending on
the package in question.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-06-27  0:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  0:42 Athena Martin via Bug reports for GNU Guix [this message]
2023-07-07 14:00 ` bug#64309: Python dlopen()s musl libc Ludovic Courtès
2023-07-08 20:16   ` Athena Martin via Bug reports for GNU Guix
2023-07-09  8:35     ` Josselin Poiret via Bug reports for GNU Guix
2023-07-09 20:22       ` Athena Martin via Bug reports for GNU Guix
2023-07-10  7:13         ` Josselin Poiret via Bug reports for GNU Guix
2023-07-10 19:47           ` Athena Martin via Bug reports for GNU Guix
2023-07-11  8:34             ` Josselin Poiret via Bug reports for GNU Guix
2023-07-11 12:43               ` Lars-Dominik Braun
2023-07-12  8:50                 ` Josselin Poiret via Bug reports for GNU Guix
2023-07-16  8:35                   ` Lars-Dominik Braun
2023-07-10 20:21           ` Athena Martin via Bug reports for GNU Guix

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20230626204230.7b3b773a@spock.hosts.alm.website \
    --to=bug-guix@gnu.org \
    --cc=64309@debbugs.gnu.org \
    --cc=secure@alm.website \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).