summaryrefslogtreecommitdiff
path: root/dev-qt/qtwebengine/qtwebengine-6.9.0-r1.ebuild
AgeCommit message (Collapse)Author
2025-05-03dev-qt/qtwebengine: depend on sys-libs/queue-standalone if muslIonen Wolkens
Closes: https://bugs.gentoo.org/955345 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2025-04-28dev-qt/qtwebengine: allow using libatomic-stubIonen Wolkens
Adapted from linked PR given hasn't been updated yet and wanted to rebuild qtwebengine with the new dependencies on my llvm-musl chroot now. [atomic-builtins] is not enough given passes -latomic either way, and not planning to try to get this fixed in chromium. Also move to DEPEND-only, doesn't seem to be linked with shared libatomic for gcc (and stub is static-only). Skipping revbump given not worth rebuilds just to be able to depclean gcc and qtwebengine-6.9.1 is not that far off. Besides it's difficult to depclean given nodejs depends on it for libatomic at the moment still. Closes: https://github.com/gentoo/gentoo/pull/41689 Thanks-to: Michal Rostecki <vadorovsky@disroot.org> Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2025-04-18dev-qt/qtwebengine: backport build fix for with gperf 3.2Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2025-04-15dev-qt/qtwebengine: ensure execstack is disabledIonen Wolkens
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>
2025-04-06dev-qt/qtwebengine: backport fix for QTBUG-133570Ionen Wolkens
Haven't reproduced the crash myself, but both falkon and qutebrowser upstreams had reports about that issue with 6.9.0, and may as well include it before potential unmasking. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>