View previous topic :: View next topic |
Author |
Message |
nenoro n00b
Joined: 07 Jan 2018 Posts: 55
|
Posted: Fri Jan 29, 2021 8:49 pm Post subject: bring back jumbo-build to qtwebengine please |
|
|
Hello
So i do like qtwebengine with jumbo-build but yesterday when my machine was compiling it was the turn of qtwebengine and at 12 am i saw the package was still compiling then i scrolled above to see why and i saw the bad news "-jumbo-build", i eixed qtwebengine and got my confirmation no more jumbo-build....
Just why i want to know who rick rolled us by removing "jumbo-build" it's my life savior when i compile qtweeb why there is no news about "hey guys sorry we have removed jumbo-build"
Who is behind this sorcery ????
instead of 1 hour and 21 minutes it will take 2 - 3 hours no thank you. |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 31258 Location: here
|
Posted: Fri Jan 29, 2021 8:58 pm Post subject: |
|
|
The qtwebengine package is based on chromium and chromium has removed jumb-build _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
nenoro n00b
Joined: 07 Jan 2018 Posts: 55
|
Posted: Fri Jan 29, 2021 9:09 pm Post subject: |
|
|
That's a bad move for real lot of people who need this will merge from gentoo to void, arch, ubuntu or else it will be painful to see another wave of people leaving the ship |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22627
|
Posted: Fri Jan 29, 2021 9:56 pm Post subject: |
|
|
This is not the appropriate venue to raise this concern. First, for a package change request, it should be directed to the Gentoo maintainers, not to the forum. Second, in this case, as fedeliallalinea described, the Gentoo maintainers are merely propagating the change made by upstream. Upstream found the feature to be too burdensome to keep, and they have such high end hardware that they don't need the feature for themselves. This could be seen as a good reason to abandon qtwebengine, at least until it slims down to a more reasonable size. |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Sat Jan 30, 2021 2:59 am Post subject: |
|
|
nenoro wrote: | That's a bad move for real lot of people who need this will merge from gentoo to void, arch, ubuntu or else it will be painful to see another wave of people leaving the ship |
How about leaving the Google ship instead? |
|
Back to top |
|
|
nenoro n00b
Joined: 07 Jan 2018 Posts: 55
|
Posted: Sat Jan 30, 2021 12:12 pm Post subject: |
|
|
Ant P. wrote: | nenoro wrote: | That's a bad move for real lot of people who need this will merge from gentoo to void, arch, ubuntu or else it will be painful to see another wave of people leaving the ship |
How about leaving the Google ship instead? |
that is what i'm planning to do avoid any package who needs qtwebengine.
Quote: | This is not the appropriate venue to raise this concern. First, for a package change request, it should be directed to the Gentoo maintainers, not to the forum. Second, in this case, as fedeliallalinea described, the Gentoo maintainers are merely propagating the change made by upstream. Upstream found the feature to be too burdensome to keep, and they have such high end hardware that they don't need the feature for themselves. This could be seen as a good reason to abandon qtwebengine, at least until it slims down to a more reasonable size. |
bug.gentoo people are already asking for a binary one they don't want their machines to die and i understand their pain |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 31258 Location: here
|
Posted: Sat Jan 30, 2021 4:03 pm Post subject: |
|
|
Ant P. wrote: | How about leaving the Google ship instead? |
In my case qtwebengine is used by calibre that there is no real alternative. _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5929
|
Posted: Sat Jan 30, 2021 4:51 pm Post subject: |
|
|
nenoro wrote: | Ant P. wrote: | nenoro wrote: | That's a bad move for real lot of people who need this will merge from gentoo to void, arch, ubuntu or else it will be painful to see another wave of people leaving the ship |
How about leaving the Google ship instead? |
that is what i'm planning to do avoid any package who needs qtwebengine.
|
so your logic is to remove gentoo altogether instead of the relevant pkgs?
on my system I need to remove only 2 pkgs in order to be able to unmerge qtwebengine
have to considered using ccache? _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
Chiitoo Administrator
Joined: 28 Feb 2010 Posts: 2728 Location: Here and Away Again
|
Posted: Sat Jan 30, 2021 4:51 pm Post subject: ><)))°€ |
|
|
The removal of jumbo-build from Chromium is actually reverted in Qt WebEngine, and it works just fine for me on 5.15.9999, but it's causing build issues for others and that is why it was removed from the ebuild for the time being.
It should return in the future as long as the build issues can be dealt with.
(The adventurous could re-enabled it themselves and see if it works or not.) _________________ Kindest of regardses. |
|
Back to top |
|
|
Hund Apprentice
Joined: 18 Jul 2016 Posts: 218 Location: Sweden
|
Posted: Sun Jan 31, 2021 7:45 am Post subject: |
|
|
Hu wrote: | This could be seen as a good reason to abandon qtwebengine, at least until it slims down to a more reasonable size. |
qutebrowser only supports Qt WebEngine. As a qutebrowser I can't imagine using anything else, it's the only sane keyboard driven web browser out there.
Ant P. wrote: | How about leaving the Google ship instead? |
Qt WebEngine has nothing to do with Google.
DaggyStyle wrote: | so your logic is to remove gentoo altogether instead of the relevant pkgs? |
He said Google, not Gentoo. :) _________________ Collect memories, not things. |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 31258 Location: here
|
Posted: Sun Jan 31, 2021 10:39 am Post subject: |
|
|
Hund wrote: | Qt WebEngine has nothing to do with Google. |
It's based on chromium so it has something to do with Google. _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Hund Apprentice
Joined: 18 Jul 2016 Posts: 218 Location: Sweden
|
Posted: Sun Jan 31, 2021 12:38 pm Post subject: |
|
|
fedeliallalinea wrote: | Hund wrote: | Qt WebEngine has nothing to do with Google. |
It's based on chromium so it has something to do with Google. |
It does, it's Google who wrote the upstream code, but what I meant is that there's nothing 'Googley' in the code in Qt WebEngine that's in anyway calling home to Google or something like that. _________________ Collect memories, not things. |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5929
|
Posted: Sun Jan 31, 2021 1:15 pm Post subject: |
|
|
Hund wrote: | DaggyStyle wrote: | so your logic is to remove gentoo altogether instead of the relevant pkgs? |
He said Google, not Gentoo. |
you are correct, ignore me.... (facepalm) _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
hunky l33t
Joined: 19 Nov 2003 Posts: 914 Location: Alaska
|
Posted: Mon Feb 01, 2021 5:53 am Post subject: |
|
|
For me, looks like the use flag widgets gets me in trouble. Without any evidence, I'm guessing widgets adds some nice functionality, like perhaps image location in Digikam, and the like.
Code: | equery depends qtwebengine
* These packages depend on qtwebengine:
kde-apps/kdenlive-20.12.1 (webengine ? >=dev-qt/qtwebengine-5.15.1:5)
kde-apps/kimagemapeditor-20.12.1 (>=dev-qt/qtwebengine-5.15.1:5[widgets])
kde-apps/marble-20.12.1 (webengine ? >=dev-qt/qtwebengine-5.15.1:5[widgets])
kde-plasma/kdeplasma-addons-5.20.5 (webengine ? >=dev-qt/qtwebengine-5.15.1:5)
kde-plasma/libksysguard-5.20.5 (webengine ? >=dev-qt/qtwebengine-5.15.1:5)
media-gfx/digikam-7.1.0-r1 (>=dev-qt/qtwebengine-5.12.3:5[widgets])
media-sound/musescore-3.6.1 (webengine ? dev-qt/qtwebengine:5[widgets])
sci-geosciences/gpsbabel-1.5.4-r1 (gui ? dev-qt/qtwebengine:5[widgets])
www-client/falkon-3.1.0-r1 (>=dev-qt/qtwebengine-5.12.3:5[widgets])
|
I have -webengine enabled, so there's that for me to be confused by. |
|
Back to top |
|
|
PlatinumTrinity Tux's lil' helper
Joined: 10 Mar 2020 Posts: 100
|
Posted: Mon Feb 01, 2021 11:21 am Post subject: |
|
|
Hund wrote: | Hu wrote: | This could be seen as a good reason to abandon qtwebengine, at least until it slims down to a more reasonable size. |
qutebrowser only supports Qt WebEngine. As a qutebrowser I can't imagine using anything else, it's the only sane keyboard driven web browser out there. |
There are firefox extensions that enable vim key bindings. Maybe look into those? |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 31258 Location: here
|
Posted: Mon Feb 01, 2021 11:46 am Post subject: |
|
|
Hund wrote: | It does, it's Google who wrote the upstream code, but what I meant is that there's nothing 'Googley' in the code in Qt WebEngine that's in anyway calling home to Google or something like that. |
Ah yes you right, sorry I misunderstanding, from qtwebengine page
Quote: | Note: Qt WebEngine is based on Chromium, but does not contain or use any services or add-ons that might be part of the Chrome browser that is built and delivered by Google. You can find more detailed information about the differences between Chromium and Chrome in this overview that is part of the documentation in the Chromium Project upstream source tree. |
_________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Hund Apprentice
Joined: 18 Jul 2016 Posts: 218 Location: Sweden
|
Posted: Mon Feb 01, 2021 5:09 pm Post subject: |
|
|
PlatinumTrinity wrote: | Hund wrote: | Hu wrote: | This could be seen as a good reason to abandon qtwebengine, at least until it slims down to a more reasonable size. |
qutebrowser only supports Qt WebEngine. As a qutebrowser I can't imagine using anything else, it's the only sane keyboard driven web browser out there. |
There are firefox extensions that enable vim key bindings. Maybe look into those? |
That's what I started with years ago. And it's fine if you want some basic Vi-like keybindings, but it's kinda like adding Vi-like keybindings for Nano compared to the real deal.
fedeliallalinea wrote: | Hund wrote: | It does, it's Google who wrote the upstream code, but what I meant is that there's nothing 'Googley' in the code in Qt WebEngine that's in anyway calling home to Google or something like that. |
Ah yes you right, sorry I misunderstanding, from qtwebengine page
Quote: | Note: Qt WebEngine is based on Chromium, but does not contain or use any services or add-ons that might be part of the Chrome browser that is built and delivered by Google. You can find more detailed information about the differences between Chromium and Chrome in this overview that is part of the documentation in the Chromium Project upstream source tree. |
|
No worries! It seems like a lot of people have the misconception that Qt Webengine is a Google product. :) _________________ Collect memories, not things. |
|
Back to top |
|
|
xahodo Tux's lil' helper
Joined: 17 May 2007 Posts: 82 Location: Gouda, the Netherlands
|
Posted: Mon Feb 01, 2021 5:47 pm Post subject: Re: bring back jumbo-build to qtwebengine please |
|
|
nenoro wrote: | instead of 1 hour and 21 minutes it will take 2 - 3 hours no thank you. |
JUST 2 - 3 hours? are you running a supercomputer or something?
On my i5 (2016) with 8GB RAM it takes a whole day! I just leave it be and come back when it's done. Even with jumbo-build it took time. |
|
Back to top |
|
|
Hund Apprentice
Joined: 18 Jul 2016 Posts: 218 Location: Sweden
|
Posted: Mon Feb 01, 2021 6:07 pm Post subject: Re: bring back jumbo-build to qtwebengine please |
|
|
xahodo wrote: | nenoro wrote: | instead of 1 hour and 21 minutes it will take 2 - 3 hours no thank you. |
JUST 2 - 3 hours? are you running a supercomputer or something?
On my i5 (2016) with 8GB RAM it takes a whole day! I just leave it be and come back when it's done. Even with jumbo-build it took time. |
That's weird. On my almost 10 year old i5-2500k with 16 GB of RAM it went from about 2.5 hours to 5.5 hours. _________________ Collect memories, not things. |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5929
|
Posted: Mon Feb 01, 2021 11:57 pm Post subject: |
|
|
dev-qt/qtwebengine-5.15.1 took me 2 hours and 24 minutes,,dev-qt/qtwebengine-5.15.2 jumped to 5 hours and 3 minutes.
I assume that this s where jumbo build was removed? _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
Hund Apprentice
Joined: 18 Jul 2016 Posts: 218 Location: Sweden
|
Posted: Tue Feb 02, 2021 4:04 am Post subject: |
|
|
DaggyStyle wrote: | dev-qt/qtwebengine-5.15.1 took me 2 hours and 24 minutes,,dev-qt/qtwebengine-5.15.2 jumped to 5 hours and 3 minutes.
I assume that this s where jumbo build was removed? |
That's correct. :) _________________ Collect memories, not things. |
|
Back to top |
|
|
wrc1944 Advocate
Joined: 15 Aug 2002 Posts: 3456 Location: Gainesville, Florida
|
Posted: Tue Feb 09, 2021 4:03 pm Post subject: |
|
|
In today's @world updates, I found: dev-qt/qtwebengine/qtwebengine-5.15.2_p20210205, and in the new ebuild lines 102-105 I found:
Code: | # QTBUG-88657 - jumbo-build is broken
#if ! use jumbo-build; then
sed -i -e 's|use_jumbo_build=true|use_jumbo_build=false|' \
src/buildtools/config/common.pri || die |
However, at the start of the emerge it still mentions jumbo build. Brief excerpts:
Code: | Checking for xtst... yes
Checking for jumbo build merge limit... 8
Checking for linker supports -z noexecstack... yes
Done running configuration tests.
Configure summary:
Qt WebEngine Build Tools:
Use System Ninja ....................... yes
Jumbo Build Merge Limit ................ 8
Developer build ........................ no
Sanitizer .............................. no |
I installed it, and it built in 2 hours 20 minutes., which is about what it does with jumbo-build IIRC. Before I started using jumbo build, it took over five hours for sure.
Apparently, having dev-qt/qtwebengine jumbo-build in package.use is still active?
That, or they've done something to speed up the compile time in qtwebengine-5.15.2_p20210205. Anyone seeing this behavior, or know more about what's going on?
I can live with 2 hours 20 minutes, on three Gentoo kde installs.
[Moderator edit: changed [quote] tags to [code] tags to preserve output layout. -Hu] _________________ Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0 |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22627
|
Posted: Tue Feb 09, 2021 5:25 pm Post subject: |
|
|
wrc1944 wrote: | Code: | # QTBUG-88657 - jumbo-build is broken
#if ! use jumbo-build; then
sed -i -e 's|use_jumbo_build=true|use_jumbo_build=false|' \
src/buildtools/config/common.pri || die |
However, at the start of the emerge it still mentions jumbo build. Brief excerpts: | I see two possibilities here. The first is that qtwebengine has both an on/off switch (which the ebuild manipulates) and a concurrency limit (which the ebuild does not manipulate, and which would only be meaningful when jumbo-build is switched on). You showed fragments telling the value of the concurrency limit, which upstream might show regardless of whether it will be meaningful.
The second possibility is that upstream changed the implementation from a switch to a counter, and the ebuild is unaware of this, and so the sed in the ebuild is now meaningless.
wrc1944 wrote: | Apparently, having dev-qt/qtwebengine jumbo-build in package.use is still active? | From the output you provided, I think USE=jumbo-build is not checked in the ebuild. However, since that is just a flag that tells the ebuild what to tell the upstream build system, it is possible for the USE flag to be ignored and for upstream to still do jumbo (or not), depending on how they wrote it. |
|
Back to top |
|
|
wrc1944 Advocate
Joined: 15 Aug 2002 Posts: 3456 Location: Gainesville, Florida
|
Posted: Wed Feb 10, 2021 3:08 am Post subject: |
|
|
FWIW, on another Gentoo install, qtwebengine emerged in 2 hours 25 minutes like the first install (same hardware, different partition), but at the end listed a few severe warnings about chromium and "command not found" incidents I didn't notice. So far, haven't noticed any random runtime failures. Wish I had noticed in the past if there had been a history of such warnings (or not) before or after I enabled jumbo-build. Are these potentially problematic?
Code: | >>> Completed installing dev-qt/qtwebengine-5.15.2_p20210205 into /var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20210205/image
* Final size of build directory: 4510268 KiB ( 4.3 GiB)
* Final size of installed tree: 209648 KiB (204.7 MiB)
* QA Notice: command not found:
*
* sh: line 1: git: command not found
* sh: line 1: git: command not found
* sh: line 1: git: command not found
* sh: line 1: git: command not found
* sh: line 1: git: command not found
* sh: line 1: git: command not found
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* ../../../../qtwebengine-5.15.2_p20210205/src/3rdparty/chromium/net/base/mime_util.cc:239:18: warning: offset ‘5’ outside bounds of constant string [-Warray-bounds]
* ../../../../qtwebengine-5.15.2_p20210205/src/3rdparty/chromium/net/base/mime_util.cc:239:18: warning: offset ‘4’ outside bounds of constant string [-Warray-bounds]
* ../../../../qtwebengine-5.15.2_p20210205/src/3rdparty/chromium/net/dns/host_resolver.cc:82:16: warning: returning reference to temporary [-Wreturn-local-addr]
* ../../../../qtwebengine-5.15.2_p20210205/src/3rdparty/chromium/third_party/webrtc/api/function_view.h:79:17: warning: the compiler can assume that the address of ‘f’ will never be NULL [-Waddress]
* Please do not file a Gentoo bug and instead report the above QA
* issues directly to the upstream developers of this software.
* Homepage: https://www.qt.io/
strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version
/usr/lib64/qt5/libexec/QtWebEngineProcess
/usr/lib64/libQt5WebEngineWidgets.so.5.15.2
/usr/lib64/libQt5WebEngine.so.5.15.2
/usr/lib64/qt5/qml/QtWebEngine/libqtwebengineplugin.so
/usr/lib64/qt5/bin/qwebengine_convert_dict
/usr/lib64/libQt5WebEngineCore.so.5.15.2
>>> Installing (4 of 4) dev-qt/qtwebengine-5.15.2_p20210205::gentoo
* Regenerating gentoo-qconfig.h
* Updating QT_CONFIG in qconfig.pri
* Updating QT.global_private in qmodule.pri
>>> Recording dev-qt/qtwebengine in "world" favorites file...
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system. |
_________________ Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0 |
|
Back to top |
|
|
wrc1944 Advocate
Joined: 15 Aug 2002 Posts: 3456 Location: Gainesville, Florida
|
Posted: Mon Mar 01, 2021 6:46 pm Post subject: |
|
|
On today's sync I noticed this:
Code: | dev-qt/qtwebengine-5.15.2_p20210224:5/5.15::gentoo [5.15.2_p20210205:5/5.15::gentoo] USE="alsa jumbo-build%* system-ffmpeg system-icu widgets -bindist -debug -designer -geolocation -kerberos -pulseaudio -test" 312,551 KiB |
On the jumbo-build%* flag the jumbo-build part is in yellow, and the %* part is in green.
Never saw this before, and am wondering what it signifies, if anything? I know the yellow means newly added, but not sure about the green %*
Possibly is the jumbo-build now officially back and enabled by default in qtwebengine?s
UPDATE: Just noticed in the new dev-qt/qtwebengine-5.15.2_p20210224 ebuild: IUSE="alsa bindist designer geolocation +jumbo-build kerberos pulseaudio +system-ffmpeg +system-icu widgets"
REQUIRED_USE="designer? ( widgets )"
Guess that answers part of my questions. What does green in the flag signify? _________________ Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0 |
|
Back to top |
|
|
|