Created attachment 872597 [details] emerge logs dev-qt/qtwebengine-6.6.0: Fails to build ModuleNotFoundError: No module named 'src.trace_processor' See the logs. I don't know if the issue is due to the fact I'm trying to use qtwebengine and other Qt6 ~arch packages on a system that also has arch packages but I'm posting just in case it's not.
Created attachment 872598 [details] emerge --info emerge --info
Hm, can't reproduce and looked a fair deal but I cannot find anything in perfetto nor chromium that could hint at the cause. Nothing upstream that'd sound like a fix either (albeit it did get some refactoring that might help in future versions). I've built 6.6.0 on a fresh (stable) desktop stage3 w/ same USE, my own ~amd64 machine, a llvm-musl ~amd64 system, and it all built fine. I guess there "could" be some unknown python-related package causing issues (perhaps from these overlays), but I have no ideas. Did you try to build it more than once? Maybe --jobs caused a rare glitch. fwiw may want to try with different MAKEOPTS for the off-chance it's a race condition too, e.g. `MAKEOPTS=-j10 emerge -1 qtwebengine:6`, but that sounds unlikely unless I'm overlooking a generated file (chromium gets built a lot too, if it is I assume it's already fixed upstream). Sorry, I don't have a workaround to offer if that does not work. I did try some EXTRA_GN args but trying to disable perfetto entirely ended mostly badly.
Created attachment 872606 [details] MAKEOPTS=-j10 emerge -1 qtwebengine:6 > broken.txt About the unknown python-related packages, that might be from other overlays. I'm using */*::OVERLAY_NAME in the package.mask of all overlays I enabled, and I'm only unmasking a few packages. So 97 ones for 31 overlays, :P. I'll post a list if you ask me so. My system is using the desktop profile + openrc stage3 (glibc+gcc). I already tried to compile a few times qtwebengine with MAKEOPTS=-j14 and it always failed, same for your proposal of using MAKEOPTS=-j10.
I see. Still can't reproduce and afraid I still don't have an idea on what might be causing this.
Did you tried to build qtwebengine-6.6.0 with those USE flags? +alsa -bindist -custom-cflags -designer -geolocation +jumbo-build -kerberos +opengl -pdfium +pulseaudio -qml -screencast +system-icu -test -vaapi +vulkan +widgets
(In reply to benoit.dufour from comment #5) > Did you tried to build qtwebengine-6.6.0 with those USE flags? > +alsa -bindist -custom-cflags -designer -geolocation +jumbo-build -kerberos > +opengl -pdfium +pulseaudio -qml -screencast +system-icu -test -vaapi > +vulkan +widgets Yes, that's what I meant by this bit when I tried it in stable: (In reply to Ionen Wolkens from comment #2) > I've built 6.6.0 on a fresh (stable) desktop stage3 w/ same USE Haven't seen anyone else run into this (yet) too, so I do suspect it's something obscure like a specific package interfering (even if it's not a dependency of qtwebengine, python ecosystem is messy). Does `grep -r PYTHONPATH /etc/env.d` return anything? Sometime overlay packages abuse that variable and end up causing problems. Albeit I already experimented a bit with that and I doubt it. Maybe something else in /usr/lib/python* but I have no idea.
grep -r PYTHONPATH /etc/env.d returns nothing. grep -r PYTHONPATH /usr/lib/python* returns something but I don't think it is useful. grep -r perfetto /usr/lib/python* returns nothing. grep -r perfetto /etc/env.d returns nothing (of course). Btw I had to install Python dev-python/pip in order to install some packages in virtualenv. And I just downgraded all Qt6 package to 6.5.2{,-r#} by masking their ~arch flags and by using this command: emerge -1av $(qlist ICS dev-qt/ | grep -i qt6). I'll tell you afterwards if this at least builds, since if it builds, we'll be able to tell if the issue is specific to qtwebengine 6.6.0.
(In reply to benoit.dufour from comment #7) > I'll tell you afterwards if this at least builds, since if it builds, we'll > be able to tell if the issue is specific to qtwebengine 6.6.0. Could be, v8 does newly make use of tracing / perfetto and could lead to triggering this (was one of the thing I seen while looking for possible causes, but did not lead to any hints as to why it would fail).
So Qt6 version 6.5.2{,-r#} fortunately did build correctly as well as dev-qt/qtwebengine-6.5.2-r1. From now, I won't try to use unstable Qt6 packages. And so I won't do further testing on that build issue by myself unless requested. Also, feel free to ask me any other file from my Gentoo setup that might help solving the issue.
The same happens on dev-qt/qtwebengine-6.6.1
Still haven't heard of anyone else running into this, so no idea what's special about your system.
nothing
Created attachment 880002 [details] My dev-qt packages. If it can help, here's the list of all my installed dev-qt packages.
I doubt it's related to other dev-qt packages, perhaps something that happens to use python instead (either some package I'm not aware of, or something that was installed manually with pip or similar). I did spend a lot of time on this bug before trying to figure out a possible cause inspecting the qtwebengine source for possible causes but couldn't figure out anything nor reproduce (and at this point I don't intend to spend more unless more people are hitting the issue, sorry).
(I'd have closed this as WORKSFORME already, but left it open for visibility in case someone else hit this which would indicate it's not specific to your system at least)
Ok. Btw it's true I installed PIP but it only allows me to install packages in my local non root packages or in VirtualEnvs.
(In reply to benoit.dufour from comment #16) > Ok. Btw it's true I installed PIP but it only allows me to install packages > in my local non root packages or in VirtualEnvs. local non-root could potentially have an impact if your user environment leaked to portage, it takes priority over system packages *if* they're found and can cause obscure issues Nowadays (this changed) our pip does not even allow installing outside virtualenvs even as non-root without passing --break-system-packages That aside, do ensure you have a clean env when using emerge, (e.g. `sudo -i`, or `su -`). May also want to check /usr/local for any stuff that shouldn't be there (normally nothing but empty directories in there). Could also try running: find /usr/lib/python* -exec qfile -o {} + That should output nothing at all in most cases. It checks if any files in your python directories are orphaned, but this (typically) only happen if you used pip or something else other than portage to install python packages as root. Even if there's nothing, still the possibility that a normally installed package (perhaps from these overlays as I mentioned before), is causing some sort of conflict. If you installed qtwebengine on a new system, or in a chroot, I doubt you'd see this issue. Not that I have a whole lot of other ideas, I'm no python expert.
The result : find /usr/lib/python* -exec qfile -o {} + /usr/lib/python3.11/__pycache__/fnmatch.cpython-311.pyc.139699237179376
That one should be harmless, you can delete it either way though -- looks like temporary junk that got left over.
Ok. I see I also installed R-Studio through dpkg but I removed it manually. It included some Qt 4 libraries.
