From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 5/7] cargo.eclass: use custom profile for all builds
Date: Thu, 9 Feb 2023 16:35:29 -0500 [thread overview]
Message-ID: <Y+VnIY+5xYsE2ilN@eversor> (raw)
In-Reply-To: <20230209204847.3270114-6-gyakovlev@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
On Thu, Feb 09, 2023 at 12:48:45PM -0800, Georgy Yakovlev wrote:
> + strip = "none"
strip was stabilized in rust-1.59, this will likely fail without
USE=nightly on older rusts and other patch is only setting >=1.57
Haven't checked other options, I just happened to remember this one.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-09 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 20:48 [gentoo-dev] cargo.eclass improvements Georgy Yakovlev
2023-02-09 20:48 ` [gentoo-dev] [PATCH 1/7] cargo.eclass: bump minimum rust to 1.57.0 Georgy Yakovlev
2023-02-09 20:48 ` [gentoo-dev] [PATCH 2/7] cargo.eclass: pass --no-track to cargo install Georgy Yakovlev
2023-02-09 20:48 ` [gentoo-dev] [PATCH 3/7] cargo.eclass: document undocumented variables, mark as readonly Georgy Yakovlev
2023-02-09 20:48 ` [gentoo-dev] [PATCH 4/7] cargo.eclass: set progress.when = "never" in config Georgy Yakovlev
2023-02-10 6:03 ` Michał Górny
2023-02-10 21:13 ` Georgy Yakovlev
2023-02-11 6:22 ` Michał Górny
2023-02-09 20:48 ` [gentoo-dev] [PATCH 5/7] cargo.eclass: use custom profile for all builds Georgy Yakovlev
2023-02-09 21:35 ` Ionen Wolkens [this message]
2023-02-10 21:15 ` Georgy Yakovlev
2023-02-09 20:48 ` [gentoo-dev] [PATCH 6/7] cargo.eclass: set codegen-units = 1 Georgy Yakovlev
2023-02-09 20:48 ` [gentoo-dev] [PATCH 7/7] cargo.eclass: filter out lto flags for C/CXX compilers Georgy Yakovlev
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=Y+VnIY+5xYsE2ilN@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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