From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: help-guix@gnu.org
Subject: Re: Packaging a python package that is using setuptools_rust
Date: Sat, 24 Oct 2020 15:54:29 +0200 [thread overview]
Message-ID: <a39ea2c4-7011-ce7c-1eaa-ced0df6507d5@crazy-compilers.com> (raw)
In-Reply-To: <80e00aa7-9ddb-4255-9d55-0393e97e84e2@www.fastmail.com>
Am 19.10.20 um 12:52 schrieb Hamzeh Nasajpour:
> running build_rust
> error: [Errno 2] No such file or directory: 'cargo'
> command "python" "-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "build" failed with status 1
This looks like cargo is not found on the path, although it should be
there. You could validate $PATH like this: Add a phase before the
build-phase, containing just "(pk (getenv PATH))".
> Do you have any idea? I should add the rust dependencies to `native-inputs` or `inputs` of `etebase-py`?
It must be a native-input, since cargo and rustc are expected to run on
the build system.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2020-10-24 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 10:52 Packaging a python package that is using setuptools_rust Hamzeh Nasajpour
2020-10-24 13:54 ` Hartmut Goebel [this message]
2020-10-25 10:16 ` Hamzeh Nasajpour
2020-10-25 10:47 ` Tobias Geerinckx-Rice
2020-10-25 11:28 ` Hamzeh Nasajpour
2020-10-25 12:26 ` Efraim Flashner
2021-12-31 8:33 ` Lars-Dominik Braun
2022-01-13 7:58 ` phodina
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=a39ea2c4-7011-ce7c-1eaa-ced0df6507d5@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.