From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rust: update to 1.64.0 [ci skip]
Date: Mon, 03 Oct 2022 22:40:13 +0200 [thread overview]
Message-ID: <20221003204013.DZUuuorOFFn-trzQaDBUcaf9SswAF2pz2ffmhwbRtAc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39673@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/39673#issuecomment-1266021219
Comment:
Looking a bit into it, I think I've got it building with our current version by setting the `profile = "user"` toplevel option which will use default options from `masterdir/builddir/rustc-1.63.0-src/src/bootstrap/defaults/config.user.toml`:
```
# These defaults are meant for users and distro maintainers building from source, without intending to make multiple changes.
[build]
# When compiling from source, you almost always want a full stage 2 build,
# which has all the latest optimizations from nightly.
build-stage = 2
test-stage = 2
doc-stage = 2
# When compiling from source, you usually want all tools.
extended = true
```
I think this would make sense to adopt those options or include `profile = "user"`. I'm still test building things while also doing firefox-esr builds in parallel so I'm not able to fully verify if every target builds fully.
next prev parent reply other threads:[~2022-10-03 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 14:21 [PR PATCH] " jcgruenhage
2022-10-03 14:39 ` Duncaen
2022-10-03 16:16 ` jcgruenhage
2022-10-03 20:40 ` Duncaen [this message]
2022-10-03 20:50 ` Duncaen
2022-10-12 19:44 ` mmnmnnmnmm
2022-10-16 17:32 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-03 8:30 ` [PR PATCH] [Merged]: " classabbyamp
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=20221003204013.DZUuuorOFFn-trzQaDBUcaf9SswAF2pz2ffmhwbRtAc@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).