From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Pradana Adrinusa AUMARS <paumars@courrier.dev>
Cc: Ricardo Wurmus <rekado@elephly.net>, help-guix@gnu.org
Subject: Re: Python subprocess fails to execute Pip-installed module
Date: Sun, 16 Oct 2022 17:50:41 +0200 [thread overview]
Message-ID: <871qr7zqw6.fsf@nckx> (raw)
In-Reply-To: <98639a5072b42ebedb57275086836d0117f44d82.camel@courrier.dev>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Hi Pradana,
Pradana Adrinusa AUMARS 写道：
> dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
And this file doesn't exist.
Prebuilt binary blobs don't mix well with Guix for this reason:
they hard-code file names such as this one.
One (brand-)new work-around is
$ guix shell -CF [PACKAGE…] [-- your command line]
E.g.,
$ guix shell -CF -- ./hello # random binary downloaded from
Debian
Hello, world!
which creates a virtual, backwards-compatible directory layout
within the container.
This is a (glorious) hack, but it's no substitute for proper Guix
packaging!
> outputs that bash cannot find this file.
That error is criminally misleading. ‘A’ file, but not ‘this’
file. :-/
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-16 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 11:38 Python subprocess fails to execute Pip-installed module Pradana Adrinusa AUMARS
2022-10-16 15:21 ` Ricardo Wurmus
2022-10-16 15:37 ` Pradana Adrinusa AUMARS
2022-10-16 15:50 ` Tobias Geerinckx-Rice [this message]
2022-10-16 18:53 ` Pradana Adrinusa AUMARS
2022-11-12 22:46 ` Python subprocess fails to execute Pip-installed module / Packaging Python Ray Pradana Adrinusa AUMARS
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=871qr7zqw6.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=paumars@courrier.dev \
--cc=rekado@elephly.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).