gentoo-mirror/gentoo
1
0
Fork 0
mirror of https://github.com/gentoo-mirror/gentoo.git synced 2026-08-24 06:48:18 -07:00
Code Issues Projects Releases Wiki Activity

dev-qt/qtwebengine: ensure execstack is disabled

Browse Source 
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>
This commit is contained in:
Ionen Wolkens
2025-04-15 01:31:05 -04:00
parent 8118d39d95
commit b2a26e9d7a
4 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
dev-qt/qtwebengine/qtwebengine-6.8.3.ebuild
View File

@@ -257,6 +257,10 @@ src_configure() {
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may
# "possibly" get enabled by some paths and cause issues (bug #953111)
append-ldflags -Wl,-z,noexecstack
export NINJAFLAGS=$(get_NINJAOPTS)
[[ ${NINJA_VERBOSE^^} == OFF ]] || NINJAFLAGS+=" -v"

4
dev-qt/qtwebengine/qtwebengine-6.9.0-r1.ebuild
View File

@@ -255,6 +255,10 @@ src_configure() {
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may
# "possibly" get enabled by some paths and cause issues (bug #953111)
append-ldflags -Wl,-z,noexecstack
export NINJAFLAGS=$(get_NINJAOPTS)
[[ ${NINJA_VERBOSE^^} == OFF ]] || NINJAFLAGS+=" -v"

4
dev-qt/qtwebengine/qtwebengine-6.9.9999.ebuild
View File

@@ -253,6 +253,10 @@ src_configure() {
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may
# "possibly" get enabled by some paths and cause issues (bug #953111)
append-ldflags -Wl,-z,noexecstack
export NINJAFLAGS=$(get_NINJAOPTS)
[[ ${NINJA_VERBOSE^^} == OFF ]] || NINJAFLAGS+=" -v"

4
dev-qt/qtwebengine/qtwebengine-6.9999.ebuild
View File

@@ -251,6 +251,10 @@ src_configure() {
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may
# "possibly" get enabled by some paths and cause issues (bug #953111)
append-ldflags -Wl,-z,noexecstack
export NINJAFLAGS=$(get_NINJAOPTS)
[[ ${NINJA_VERBOSE^^} == OFF ]] || NINJAFLAGS+=" -v"