| Age | Commit message (Collapse) | Author |
|---|
|
Just to be in sync with other ebuilds and propagate to new users.
Skipping revbump is not "correct" but:
1. qtwebengine-6.9.1 is due soon (May 15 if not delayed), and won't
be masked unlike 6.9.0 (which already has :=)
2. assume new libxml2 won't be unmasked before then outside testing
3. for stable, 6.9.1 will likely be stabilized before new libxml2,
and then 6.8.2+6.8.3 will be removed from the tree.
For special cases, e.g. users unmasking for testing or using the
new libxml2 in stable, then can let preserved-rebuild do its thing
rather than make *everyone* do a very large rebuild for likely nothing.
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>
|
|
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
Signed-off-by: Arthur Zamarin <arthurzam@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>
|
|
Same issue that chromium ran into wrt bug #951816
Bug: https://bugs.gentoo.org/951816
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Or probably clang-20 anyway, haven't confirmed that 19 works
for 6.8.3 (but definitely fine for 6.8.2, and the same bit of
code exists in it).
On that note, qtwebengine-6.8.2 is probably affected too, but
6.8.3 "should" be stabilized before clang-20 and it saves having
to test+change stable 6.8.2 for this.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
