From: phodina via <help-guix@gnu.org>
To: help-guix <help-guix@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Efraim Flashner <efraim@flashner.co.il>
Subject: Specifying rust version
Date: Mon, 26 Dec 2022 09:00:40 +0000 [thread overview]
Message-ID: <DU5DmPh22bC-vKOvf2SArRg1pwTtPNBReJwvQzmN8pXiPvzrfW0f0fO4jL9_pVCKgqL-6VW0ZFOu8RCYZIFFe4-D9g0vM8u01YHIbAMqIjs=@protonmail.com> (raw)
In-Reply-To: <9HPT231QhmBHf-sXMAX0HcaUXokVCH-pKqntxd3QLQ4aH53EYk4soFhngqkdfsasYo-0g7JFk8zZhMInQgGwQBRsd19OWvc1y1PadBYTjlg=@protonmail.com>
Hi,
the documentation for 'cargo-build-system' [1] refers to parameter '#:rust' which allows user to specify the Rust compiler version.
However, I've found this commit 9635119a61a9ab1b023558727fcdf1816fdc7fc6 from Maxim which makes all 'rust-.*' definitions private.
Is there a way to specify newer Rust compiler? Something like 'rust-next'?
The package requires version 1.62 but the current is 1.60. Also both version are already defined. What's missing is just way to select them.
[1] https://guix.gnu.org/manual/en/html_node/Build-Systems.html
EDIT: Add help-guix@gnu.org to list of recipients.
----
Petr
------- Forwarded Message -------
From: phodina <phodina@protonmail.com>
Date: On Monday, December 26th, 2022 at 9:39 AM
Subject: Specifying rust version
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, Efraim Flashner <efraim@flashner.co.il>
> Hi,
>
> the documentation for 'cargo-build-system' [1] refers to parameter '#:rust' which allows user to specify the Rust compiler version.
>
> However, I've found this commit 9635119a61a9ab1b023558727fcdf1816fdc7fc6 from Maxim which makes all 'rust-.*' definitions private.
>
> Is there a way to specify newer Rust compiler? Something like 'rust-next'?
>
> The package requires version 1.62 but the current is 1.60. Also both version are already defined. What's missing is just way to select them.
>
> [1] https://guix.gnu.org/manual/en/html_node/Build-Systems.html
>
> ----
> Petr
next parent reply other threads:[~2022-12-26 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9HPT231QhmBHf-sXMAX0HcaUXokVCH-pKqntxd3QLQ4aH53EYk4soFhngqkdfsasYo-0g7JFk8zZhMInQgGwQBRsd19OWvc1y1PadBYTjlg=@protonmail.com>
2022-12-26 9:00 ` phodina via [this message]
2022-12-27 6:53 ` Specifying rust version Efraim Flashner
2022-12-27 14:40 ` Maxim Cournoyer
2022-12-27 16:00 ` phodina
2022-12-27 17:34 ` Maxim Cournoyer
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='DU5DmPh22bC-vKOvf2SArRg1pwTtPNBReJwvQzmN8pXiPvzrfW0f0fO4jL9_pVCKgqL-6VW0ZFOu8RCYZIFFe4-D9g0vM8u01YHIbAMqIjs=@protonmail.com' \
--to=help-guix@gnu.org \
--cc=efraim@flashner.co.il \
--cc=maxim.cournoyer@gmail.com \
--cc=phodina@protonmail.com \
/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).