From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Athena Martin" <secure@alm.website>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 64309@debbugs.gnu.org
Subject: bug#64309: Python dlopen()s musl libc
Date: Sun, 09 Jul 2023 10:35:03 +0200 [thread overview]
Message-ID: <87v8et8oug.fsf@jpoiret.xyz> (raw)
In-Reply-To: <20230708161658.25be509c@spock.hosts.alm.website>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Hi Athena,
Athena Martin via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> On an Alpine Linux Edge host, I reproduce with:
>
> $ guix install python-neovim-remote
> $ nvr
>
> It's possible that there's some quirk of my specific environment.
>
> (I'm currently in the process of switching to Guix System so I may not
> be able to reproduce this forever.)
Can you do `LD_DEBUG=libs nvr` so that we get a log of what ld's trying
to load?
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-07-09 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 0:42 bug#64309: Python dlopen()s musl libc Athena Martin via Bug reports for GNU Guix
2023-07-07 14:00 ` 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 [this message]
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=87v8et8oug.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=64309@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludo@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).