When trying to compile (with clang-18 on a LLVM profile) I found that this package does not compile due to trivial things that are easily corrected. I am providing patches for this version to be compiled/used in Gentoo (not sure if upstream fixed them or how to provide them the patches), in any case this is a quickfix to have it compiled for now. Btw: The Gentoo's ebuild is also missing `eapply_user` at the end of `src_prepare` function
Created attachment 903388 [details, diff] Fix noexcept and throw missing specifications
Created attachment 903389 [details] Patchset to make it compile
(In reply to David Carlos Manuelda from comment #0) > Btw: The Gentoo's ebuild is also missing `eapply_user` at the end of > `src_prepare` function It is not, qt5-build_src_prepare at the end of it runs "default" which in turn does eapply_user. When using portage it's actually impossible for it to be missing in current EAPIs given a QA check will abort the build if it wasn't ran.
(In reply to Ionen Wolkens from comment #3) > (In reply to David Carlos Manuelda from comment #0) > > Btw: The Gentoo's ebuild is also missing `eapply_user` at the end of > > `src_prepare` function > It is not, qt5-build_src_prepare at the end of it runs "default" which in > turn does eapply_user. When using portage it's actually impossible for it to > be missing in current EAPIs given a QA check will abort the build if it > wasn't ran. Ah, sorry, I was too busy to notice that (and the mistake was mine on a bad folder for my custom patches that was not being applied)
Created attachment 914192 [details] build.log I'm having a similar issue. I will try the patch files shortly.
Created attachment 914193 [details] after-patch (In reply to gentoo.unbraided554 from comment #5) > Created attachment 914192 [details] > build.log > > I'm having a similar issue. > I will try the patch files shortly. Patch did not work.
I've reviewed the patches and compilation and sadly it will not compile with LLVM19 as of the char_traits missing template and other errors that are not covered by these patches. I could remove the Base::template references (that seems they don't work with clang) but the issue about char_traits persists
Note that when I tested it compiled fine with clang18 and these patches but now clang19 is another issue
FWIW I can confirm (a) it doesn't compile without the patches, and (b) it compiles with the patches and LLVM/clang 18. I didn't try with 19. I can also confirm it runs OK! It's useful qtwebengine:15 still exists for now, as app-office/kmymoney absolutely requires it at the moment.
*** Bug 947219 has been marked as a duplicate of this bug. ***
Some info for those searching and come across this bug looking for a workaround/solution. I got it working using clang-18 and the patches from this bug report. GCC will ICE on me due to the zenv1 hardware bug, so I had to figure out how to build with clang. Make a directory at "/etc/portage/patches/dev-qt/qtwebengine:5" and put the patches from this bug report there. Note that "/etc/portage/patches/dev-qt/qtwebengine-5.15.14" and "/etc/portage/patches/dev-qt/qtwebengine-5" will not work. Portage bug?? Create a file, /etc/portage/env/compiler-clang-18.conf with the following: # clang 18, use when clang 19 is failing. CC="clang-18" CPP="clang-cpp-18" # necessary for xorg-server and possibly other packages CXX="clang++-18" AR="/usr/lib/llvm/18/bin/llvm-ar" NM="/usr/lib/llvm/18/bin/llvm-nm" RANLIB="/usr/lib/llvm/18/bin/llvm-ranlib" Then create /etc/portage/env/clang-webengine.conf with: # needed for qtwebengine LDFLAGS="${LDFLAGS} -fuse-ld=lld -rtlib=compiler-rt -unwindlib=libunwind -Wl,--as-needed" EXTRA_GN="use_lld=true is_clang=true clang_use_chrome_plugins=false" Then add to /etc/portage/package.env the following: dev-qt/qtwebengine:5 compiler-clang-18.conf clang-webengine.conf There will be a ton of warnings like: warning: unknown warning option '-Wshift-overflow=2'; did you mean '-Wshift-overflow'? [-Wunknown-warning-option] warning: unknown warning option '-Wduplicated-cond' [-Wunknown-warning-option] warning: unknown warning option '-Wno-stringop-overflow'; did you mean '-Wno-shift-overflow'? [-Wunknown-warning-option] but the build will finished and can be safely ignore for now until more patches are needed.
