unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Athena Martin <secure@alm.website>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 64309@debbugs.gnu.org
Subject: bug#64309: Python dlopen()s musl libc
Date: Mon, 10 Jul 2023 09:13:32 +0200	[thread overview]
Message-ID: <87pm508cir.fsf@jpoiret.xyz> (raw)
In-Reply-To: <20230709162221.39fb0e66@spock.hosts.alm.website>

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

Hi Athena,

So it's not the LD_DEBUG output that hold a clue, but rather the Python
traceback.

Athena Martin <secure@alm.website> writes:

>   File "/gnu/store/dsgxdqs620pp284bfm1drbsjqpb36i4n-python-neovim-remote-2.5.1/bin/.nvr-real", line 4, in <module>
>     import nvr.nvr as mod
>   File "/home/alm/.local/lib/python3.10/site-packages/nvr/__init__.py", line 1, in <module>
>     from .nvr import main
>   File "/home/alm/.local/lib/python3.10/site-packages/nvr/nvr.py", line 34, in <module>
>     import psutil
>   File "/home/alm/.local/lib/python3.10/site-packages/psutil/__init__.py", line 102, in <module>
>     from . import _pslinux as _psplatform
>   File "/home/alm/.local/lib/python3.10/site-packages/psutil/_pslinux.py", line 26, in <module>
>     from . import _psutil_linux as cext
> ImportError: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory

The nvr package in ~/.local seems to be used instead of a Guix package.
That locally installed nvr package expects to use the host's libc, but
since the python interpreter being used has a fixed RPATH and system
search path it won't find it.

.nvr-real should definitely be using the Python code inside the store, I
wonder why that isn't being done.  Maybe our sitecustomize.py is
misbehaving?  Can you do `guix shell python-neovim-remote python --
python3` then type `import sys.path; sys.path`?

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  reply	other threads:[~2023-07-10  7:14 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
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 [this message]
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=87pm508cir.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).