diff options
| author | Ionen Wolkens <ionen@gentoo.org> | 2025-04-15 01:31:05 -0400 |
|---|---|---|
| committer | Ionen Wolkens <ionen@gentoo.org> | 2025-04-15 01:41:44 -0400 |
| commit | b2a26e9d7a8bb0a747e00ca1e28b5ad085eb9ae8 (patch) | |
| tree | f25bcf71f3bbc3c5ceadc485c7ef1fcebbc3af97 /dev-qt/qtwebengine/qtwebengine-6.8.2-r1.ebuild | |
| parent | 8118d39d958e70e4f0c3d9afe929aabcfe393b1a (diff) | |
| download | gentoo-b2a26e9d7a8bb0a747e00ca1e28b5ad085eb9ae8.tar.gz gentoo-b2a26e9d7a8bb0a747e00ca1e28b5ad085eb9ae8.tar.bz2 gentoo-b2a26e9d7a8bb0a747e00ca1e28b5ad085eb9ae8.zip | |
dev-qt/qtwebengine: ensure execstack is disabled
On second thought, think would rather ensure that this is disabled
even if do not know how it happened in the first place, especially
given chromium itself relies on noexecstack rather than notes, but
then qtwebengine does not pass it for the final linking phase.
Believe this is only an issue for qtwebengine with its multitude
of asm files that may or may not be used, so not doing it in the
eclass.
Not revbumping given it seems to only happen in edge cases, but may
as well get this done before stable 6.8.3 so that if glibc-2.41 is
stabled later it'll ensure it's fine for them.
Closes: https://bugs.gentoo.org/953111
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-qt/qtwebengine/qtwebengine-6.8.2-r1.ebuild')
0 files changed, 0 insertions, 0 deletions