View previous topic :: View next topic |
Author |
Message |
Jojobinha_2009 Tux's lil' helper
Joined: 27 Mar 2021 Posts: 77 Location: Brazil
|
Posted: Fri Apr 30, 2021 3:52 pm Post subject: dev-qt/qtwebengine Will stop compiling without errors. |
|
|
I believe this has something to do with recent compiler updates (GCC 11 for example)...
QtWebengine, which is required by kdenetwork-meta, will start emerging... and after a while it seems to just shut down.
CPU/RAM/Disk activity grounds to a halt, Portage seems to be sitting there doing nothing.
BTW this is is what is causing the Portage hangs I've reported earlier.
Earlier qtwebengine version fails to compile straight away, the newer one doesn't technically fail, but won't finish compiling either.
It just sits there emerging forever... The CPU cooler is quiet and the "load average" values sit at 0.00.
No errors are reported. _________________ Intel Core i5-9400F / 24GB DDR4 2666MHz / GeForce GTX 1060 3GB
Powered by Gentoo for x86_64
======================================================
Seize the day, and remember to have fun! |
|
Back to top |
|
|
alamahant Advocate
Joined: 23 Mar 2019 Posts: 3879
|
Posted: Fri Apr 30, 2021 3:57 pm Post subject: |
|
|
I Quote: | believe this has something to do with recent compiler updates (GCC 11 for example)... |
Try with a stable version then......
_________________
|
|
Back to top |
|
|
mike155 Advocate
Joined: 17 Sep 2010 Posts: 4438 Location: Frankfurt, Germany
|
Posted: Fri Apr 30, 2021 4:03 pm Post subject: |
|
|
Take a look at the handbook: https://wiki.gentoo.org/wiki/Handbook:AMD64/Portage/Branches
Quote: | Testing
[...]
The testing branch is exactly what it says - Testing. If a package is in testing, it means that the developers feel that it is functional but has not been thoroughly tested. Users using the testing branch might very well be the first to discover a bug in the package in which case they should file a bug report to let the developers know about it.
Beware though; using the testing branch might incur stability issues, imperfect package handling (for instance wrong/missing dependencies), too frequent updates (resulting in lots of building) or broken packages. Users that do not know how Gentoo works and how to solve problems, we recommend to stick with the stable and tested branch. |
|
|
Back to top |
|
|
Jojobinha_2009 Tux's lil' helper
Joined: 27 Mar 2021 Posts: 77 Location: Brazil
|
Posted: Fri Apr 30, 2021 4:26 pm Post subject: |
|
|
[quote="alamahant"]I Quote: | believe this has something to do with recent compiler updates (GCC 11 for example)... |
Try with a stable version then......
[/quote
I am aware that these issues can happen in the Testing branch.
This post was just a heads up.
Well, the workaround is to just avoid anything that requires qtwebengine for now _________________ Intel Core i5-9400F / 24GB DDR4 2666MHz / GeForce GTX 1060 3GB
Powered by Gentoo for x86_64
======================================================
Seize the day, and remember to have fun! |
|
Back to top |
|
|
Josef.95 Advocate
Joined: 03 Sep 2007 Posts: 4546 Location: Germany
|
|
Back to top |
|
|
Jojobinha_2009 Tux's lil' helper
Joined: 27 Mar 2021 Posts: 77 Location: Brazil
|
Posted: Fri Apr 30, 2021 9:22 pm Post subject: |
|
|
Geez that was fast.
So, when I try emerging qtwebengine again, this new patch will be pulled in automatically, right? _________________ Intel Core i5-9400F / 24GB DDR4 2666MHz / GeForce GTX 1060 3GB
Powered by Gentoo for x86_64
======================================================
Seize the day, and remember to have fun! |
|
Back to top |
|
|
Josef.95 Advocate
Joined: 03 Sep 2007 Posts: 4546 Location: Germany
|
Posted: Fri Apr 30, 2021 9:58 pm Post subject: |
|
|
Jojobinha_2009 wrote: | So, when I try emerging qtwebengine again, this new patch will be pulled in automatically, right? |
Yes, but best is, make first a fresh emerge --sync
/edit: but yes, you can check it first: example: | josef@lucy ~ $ ebuild `equery w qtwebengine` clean prepare
* qtwebengine-5.15.2_p20210406.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
* Using python2.7 to build
>>> Unpacking source...
>>> Unpacking qtwebengine-5.15.2_p20210406.tar.xz to /var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20210406/work
>>> Source unpacked in /var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20210406/work
>>> Preparing source in /var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20210406/work/qtwebengine-5.15.2_p20210406 ...
* Applying qtwebengine-5.15.0-disable-fatal-warnings.patch ...
patching file src/buildtools/config/common.pri
Hunk #1 succeeded at 26 with fuzz 1 (offset 1 line). [ ok ]
* Applying qtwebengine-5.15.2_p20210224-chromium-87-v8-icu68.patch ... [ ok ]
* Applying qtwebengine-5.15.2_p20210224-disable-git.patch ... [ ok ]
* Applying qtwebengine-5.15.2_p20210406-glibc-2.33.patch ... [ ok ]
* Applying qtwebengine-5.15.2_p20210406-gcc11.patch ... [ ok ]
* Applying qtwebengine-5.15.2_p20210406-icu69.patch ... [ ok ]
>>> Source prepared.
josef@lucy ~ $ ebuild `equery w qtwebengine` clean
josef@lucy ~ $ |
|
|
Back to top |
|
|
|