summaryrefslogtreecommitdiff
path: root/dev-db/mysql/mysql-5.7.41.ebuild
diff options
context:
space:
mode:
authorSam James <sam@gentoo.org>2023-01-18 01:10:02 +0000
committerSam James <sam@gentoo.org>2023-01-18 21:48:58 +0000
commit92c1834342000220f71cf7e9b9ad0ed111d9e084 (patch)
tree50247a6b7d22c9439044dd2771c441c618009bb7 /dev-db/mysql/mysql-5.7.41.ebuild
parent5c0ec70e210381cdc447bef4343b9555102ca7d1 (diff)
downloadgentoo-92c1834342000220f71cf7e9b9ad0ed111d9e084.tar.gz
gentoo-92c1834342000220f71cf7e9b9ad0ed111d9e084.tar.bz2
gentoo-92c1834342000220f71cf7e9b9ad0ed111d9e084.zip
dev-qt/qtcore: pass -fno-stack-clash-protection with Clang
With Clang, -fstack-clash-protection seems to lead to qtcore being miscompiled and e.g. kde-frameworks/syntax-highlighting failing to compile. It's hard to justify spending that much time investigating this for Qt 5 given it's likely it doesn't occur with Qt 6 (significant changes all over the place) and its build system is far more amenable to building with various sanitisers. Given this only happens with Clang, we can likely chalk this up to a Clang bug, but Qt is huge, and I don't have the time to try minimise this - help welcome if someone fancies it! This has probably been latent for quite a long time, but got exposed by sys-devel/clang-runtime recently starting to pass -fstack-clash-protection by default to match GCC's behaviour in Gentoo in the new upcoming (WIP) 23.0 profiles. Thanks in particular to Jonas Rakebrandt <xarblu@protonmail.com> for putting the work in to find the trigger. Bug: https://bugs.gentoo.org/865339 KDE-Bug: https://bugs.kde.org/show_bug.cgi?id=462084 KDE-Bug: https://bugs.kde.org/show_bug.cgi?id=464140 Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-db/mysql/mysql-5.7.41.ebuild')
0 files changed, 0 insertions, 0 deletions