From: phodina <phodina@protonmail.com>
To: Mohamed Amine LEGHERABA <mlegheraba@protonmail.com>
Cc: help-guix <help-guix@gnu.org>, raingloom <raingloom@riseup.net>
Subject: Re: How to use/install rust nightly on guix ?
Date: Tue, 01 Nov 2022 10:04:09 +0000 [thread overview]
Message-ID: <bU-gNFCFDPDmg4jtp_QFTx0sOAzBRDNepfNrhWGD3uVO-x_V_8APytbs429H1GGmvHYlKsZC-KSXXYZyU6B2-OMbngrdnkJrXufi79voiy4=@protonmail.com> (raw)
In-Reply-To: <0BczrmJbymhlC1HT8reRuMqtiAS4oHb0XONP-HIHbdrHzpjJTH_li3QNbaFQjpHZ_Teb3vePUKzV7gL9TGUSq5Fo_VcnCBobNsdJqRjSUGw=@protonmail.com>
Hi,
> Hello guys,
> Any ideas for the best way to install rust nightly on guix ? I don't find it in the guix channel, neither rustup.
> I need rust nightly to compile a certain project (this one : https://github.com/paritytech/substrate).
>
> Thanks,
> Mohamed Amine LEGHERABA
Not sure it's what you asked but my workflow with Rust is to create/clone Rust package. Then create Guix package with source pointing to that directory and adding all the build dependencies (plus all other fields package should have).
The last part is to enable the RUSTC_BOOTSTRAP=1 environment variable in the arguments after unpack phase. [1]
> The build system sets RUSTC_BOOTSTRAP=1. This special variable means to break the stability guarantees of rust: Allow using #![feature(...)] with a compiler that's not nightly. This should never be used except when bootstrapping the compiler.
It's a hack that works for now but haven't found a better way yet.
Last step is to run:
guix shell -D PKG
This gives you environment to test the build locally.
----
Petr
prev parent reply other threads:[~2022-11-01 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 12:29 How to use/install rust nightly on guix ? Mohamed Amine LEGHERABA via
2022-10-29 12:31 ` (
2022-10-29 16:13 ` Csepp
2022-10-29 20:57 ` Re : " Mohamed Amine LEGHERABA
2022-10-31 1:05 ` Csepp
2022-10-29 18:08 ` Sergiu Ivanov
2022-11-01 10:04 ` phodina [this message]
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='bU-gNFCFDPDmg4jtp_QFTx0sOAzBRDNepfNrhWGD3uVO-x_V_8APytbs429H1GGmvHYlKsZC-KSXXYZyU6B2-OMbngrdnkJrXufi79voiy4=@protonmail.com' \
--to=phodina@protonmail.com \
--cc=help-guix@gnu.org \
--cc=mlegheraba@protonmail.com \
--cc=raingloom@riseup.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).