diff options
| author | Ionen Wolkens <ionen@gentoo.org> | 2025-11-20 17:20:34 -0500 |
|---|---|---|
| committer | Ionen Wolkens <ionen@gentoo.org> | 2025-11-20 17:30:48 -0500 |
| commit | e4f853b3c73ddaf91ee168c3f9aee3d30bcf6bfa (patch) | |
| tree | 4a62251d5d4acadc873eda16ef811f41855a49f9 /dev-python/async-timeout/async-timeout-5.0.1.ebuild | |
| parent | 9e4b716f0e22d3cb30c5b0cb796aee1ce9eaed79 (diff) | |
| download | gentoo-e4f853b3c73ddaf91ee168c3f9aee3d30bcf6bfa.tar.gz gentoo-e4f853b3c73ddaf91ee168c3f9aee3d30bcf6bfa.tar.bz2 gentoo-e4f853b3c73ddaf91ee168c3f9aee3d30bcf6bfa.zip | |
dev-qt/qtbase: warn about USE=custom-cflags if have rdrnd
Wouldn't hurt given those that have that enabled and had it working
fine may not realize that it's related. For new installs it's less
of an issue though, so don't think need to keep this forever.
Alternatively could workaround, but I don't want to play in that
film again and would rather encourage users to turn this off unless
they really need it.
As a reminder, for Qt, USE=-custom-cflags does *not* run strip-flags
except for qtwebengine. It's a different form of modifications only
targeting some simd and similar flags, and other flags will be kept
(albeit it does strip LTO unless Qt >=6.10 + >=gcc-15.2 or clang-any
where lto bugs no longer been occurring).
Bug: https://bugs.gentoo.org/966289
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-python/async-timeout/async-timeout-5.0.1.ebuild')
0 files changed, 0 insertions, 0 deletions