diff options
| author | James Le Cuirot <chewi@gentoo.org> | 2024-08-07 15:27:36 +0100 |
|---|---|---|
| committer | James Le Cuirot <chewi@gentoo.org> | 2024-08-08 10:00:08 +0100 |
| commit | 27d469a2114b4ad0b3e682854c50c806753eb472 (patch) | |
| tree | 75f7317a1536a3730c7aab411526c2c73dd9c74e /dev-java/javahelp/javahelp-2.0.05_p20170719-r4.ebuild | |
| parent | dc27a1bba5cbcb906e93c0cd857b7e9bd08946e7 (diff) | |
| download | gentoo-27d469a2114b4ad0b3e682854c50c806753eb472.tar.gz gentoo-27d469a2114b4ad0b3e682854c50c806753eb472.tar.bz2 gentoo-27d469a2114b4ad0b3e682854c50c806753eb472.zip | |
cargo.eclass: Change RUSTFLAGS approach following recent build failures
Cargo turned out to be even worse at handling flags than I thought.
Target-specific flags set by projects were overriding our own, and Cargo
was bailing out when faced with merging a string of flags with an array
of flags.
After weighing up the poor set of options, I've found that it is better
to always set flags via a target-specific environment variable for
reasons set out in comments added here. This approach was previously
just used for cross-compiling, but now we do it unconditionally.
It has the downside of overriding generic [build] flags set by projects,
but these were already being overridden by users and ebuilds setting
RUSTFLAGS themselves.
Closes: https://bugs.gentoo.org/937453
Closes: https://bugs.gentoo.org/937470
Signed-off-by: James Le Cuirot <chewi@gentoo.org>
Diffstat (limited to 'dev-java/javahelp/javahelp-2.0.05_p20170719-r4.ebuild')
0 files changed, 0 insertions, 0 deletions