| Age | Commit message (Collapse) | Author |
|---|
|
6.9-8 -> 6.9-9:
Added:
- clang21.patch (imported from files/)
- missing-includes.patch (bug #962555)
6.10-2 -> 6.10-3:
Added:
- clang21.patch (imported from files/)
Closes: https://bugs.gentoo.org/962555
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Forgot that it needs an additional revert that wasn't in
6.9.2, else hits a build failure due to missing headers.
Also fix the commit link in the old patch.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Unbundles openh264, only used if webengine_proprietary_codecs
is enabled meaning bindist not being set.
wrt SBOM, cmake files were failing to generate with it and haven't
spent more time on this (it'd likely work if had spdx-tools which
seems unpackaged, this is the fallback path) -- not super important
(for us) so let's just disable for now.
wrt new skipped test, this is a new test that fails only with one
of *-sandbox (haven't narrowed it down given it's tedious with
qtwebengine)
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Untested given I do not have the required hardware to reproduce,
but doing this seems to have worked for Arch.
Closes: https://bugs.gentoo.org/962055
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Imagine Qt will backport from chromium as well and it'll conflict
later, but just to be sure it does not get forgotten.
Not touching stable 6.9.1, this will be stabilized long before
clang-21 is and haven't verified this all that closely.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-7 -> 6.9-8 and 6.10-1 -> 6.10-2 changes:
Added:
- perfetto-pythonpath.patch (bug #915615)
Bug: https://bugs.gentoo.org/915615
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Also cleanup xml REQ_USE, for 11..14 that USE is gone.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Minor changes from testing 6.9.9999 a bit in prepration for
6.9.2, haven't tested 6.10 again yet so required changes may
be incomplete there.
- gperf patch is upstreamed in 6.9.9999 too now
- workaround some new broken user_facing .txt, only tested
6.9.9999 but assuming 6.10/11 have the same problem right now
- tentatively drop the race condition workaround, a new
"DEPENDS WebEngineCore_sync_headers" has appeared in 6.9.9999 and
that may or may not be enough to make that obsolete but I have no
real way to test for sure, will re-add if we get reports
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
On second thought, will set this in the eclass. Affects at least one
more package (qtmultimedia), and unused or replaced CMakeLists.txt is
a common trend in Qt and this may be volatile. If something breaks
with cmake-4, would rather that it just breaks rather than do the =3.5
workaround and will fix it then.
This reverts commit 73194358936565f89dcd99b29d74627cdbb99b0e.
Bug: https://bugs.gentoo.org/957476
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Was tempting to just set it in the eclass, but only two
packages it looks like.
Closes: https://bugs.gentoo.org/957476
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-{4,5} -> 6.9-{6,7} changes:
Updated:
- cstdint.patch (several more added for gcc-16)
May possibly be more missing for USE=-jumbo-build but have
not tried that.
Closes: https://bugs.gentoo.org/957200
Thanks-to: tdr
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-4 -> 6.9-5 changes:
Updated:
- gn-bootstrap.patch (drop NINJAFLAGS chunk)
While fixing an issue to conditionally pass -v to ninja, Qt
interestingly added support for the same env var (NINJAFLAGS)
that we were adding.
Unsure if upstream's support works right though (not tested), it
uses simple string replacement rather than separate_arguments().
Could imagine potentially causing issues if NINJAFLAGS had double
spaces inherited from users setting NINJAOPTS.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Closes: https://bugs.gentoo.org/955345
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
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>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
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>
|
|
6.9-3 -> 6.9-4 changes:
Updated:
- musl-no-execinfo.patch
As usual only tend to test musl (+clang/libcxx) with .0 release
and there was one minor build failure due to a new execinfo-related
function not being guarded by #if/#endif.
Runtime also seems fine on llvm-musl, qutebrowser-9999 test pass
and can browse normally as well.
Still not including the other patches given they (hopefully)
shouldn't be that long lived.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Just so it's propagated when do bumps and reduce amount of revbumps
needed later (given qtwebengine is a huge package), it will be needed
whenever libxml2-2.14 is added & keyworded/unmasked with a new soname.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Same issue that chromium ran into wrt bug #951816
Bug: https://bugs.gentoo.org/951816
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Does not build without anymore due to some lacking guards
in tests, but it's not worth worrying with and may as well
require it (arguably this USE shouldn't even exist and be
hard enabled).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Seems to be lacking some guards against the other options,
but it doesn't really make sense for the ebuild to rely on
these and should just not pass when the main switch is off.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-2 -> 6.9-3 changes:
Updated:
- cstdint.patch (add a minor known missing include)
Likely still not final, but just a minor update before 6.9.0-rc.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Kind of forgot strip-flags no longer filters lto. Not that it was
*needed* given qt6-build.eclass filters lto either way but these
should be considered separate issues (aka, we may drop it from
qt6-build.eclass in the future but keep it in qtwebengine, or at
least when using gcc).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
9GB is "enough" but rather borderline (last build 8.9GB), and
may be a problem depending on USE+*FLAGS. Let's put it a 1GB
over to safe.
Also actually links with udev in 6.9+ now.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
I'd assume may not be needed for that long, but just so
don't forget about this. Was testing 6.9.9999 and wondering
why tst_origins was failing (it was this).
At least means that the test suite does pick this up.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-1 -> 6.9-2 changes:
Removed:
* missing-prefinalizer.patch (upstreamed)
* no-vulkan-build.patch (upstreamed)
Plus rebasing where needed. This is due to Qt bumping baseline chromium
again in 6.9, it is now based on chromium-130.
This is still only preliminary updates just so patches applies and still
needs proper testing, will be checked using 6.9.0-rc when it releases.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
I see a change that is likely to prevent the race condition
issues, but not 100% sure.
cstdint.patch is upstreamed in >=6.9, still needed for 6.8.
6.9 newly needs nodejs[icu] or else it'll fail on some regex syntax
error (likely due to use of unicode bits in it). www-client/chromium
depends on nodejs[inspector] instead which itself depends on icu+ssl
(that we do need), but we do not seem to need inspector.
Also add [icu] to 6.8.9999 just-in-case, odds are won't be testing -icu
anymore and may miss something and no harm in having users set it for
6.8.3 before 6.9.0 drops
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Formerly left disabled given nothing in the tree needed it and it was
just an oddity, but some packages started to use it now (skanpage and
upcoming frescobaldi bump through pyqt6) and it is annoying to find
out that you need to rebuild qtwebengine to enable it.
It does add a bit to the compile time and size making it wasteful for
"most" users but it is ultimately kind of negligible in relation to
webengine itself.
Doing it live-only to spare a rebuild, will be for next bump.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Seeing distros that use system's ffmpeg (like Arch) hit obscure
issues while it works on Gentoo. Like some mp3 or opus files not
playing. In case of mp3, Qt had to do a workaround for system
ffmpeg to ensure it picks the right mp3 decoder given chromium
does not support the others. Opus case is unclear still.
If we ever switch to system (patched) ffmpeg (which would be nice
on paper esp. for binpkg due to USE=bindist), it should probably
use extra consideration and also be kept optional to debug.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
