Do we really need 24GiB of ram for dev-qt/qtwebengine-5.15.8

[<3]

qtwebengine just gets more and more bloated everyday.

I have been trying to update world for the past few days, and every time portage gets stuck on something. I didn't have the time to look into it, until now. *Sigh*, qtwebengine again! This time because I don't have 24GiB of Ram! I am running on a system with 16GB of memory and 16GM of swap, both of which I thought would be plenty. Please tell me that this is left over junk from a dirty April Fools joke that the Gentoo devs played on unsuspecting users and that this will disappear once I sync again! Do I really need to upgrade my ram in order to compile qt-webengine. Does KDE plasma really need 24GiB of free ram in order to compile it?

Code: Select all

>>> Running pre-merge checks for dev-qt/qtcore-5.15.8-r4
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux-5.15.41-gentoo
 * Found kernel object directory:
 *     /usr/src/linux-5.15.41-gentoo
 * Found sources for kernel version:
 *     5.15.41-gentoo

>>> Running pre-merge checks for dev-qt/qtwebengine-5.15.8_p20230313
 * Checking for at least 24 GiB RAM ...                                                                                                                                                                                                                                                      [ !! ]
 * There is NOT at least 24 GiB RAM
 * Checking for at least 7 GiB disk space at "/var/tmp/portage/dev-qt/qtwebengine-5.15.8_p20230313/temp" ...                                                                                                                                                                                 [ ok ]
 * Checking for at least 150 MiB disk space at "/usr" ...                                                                                                                                                                                                                                    [ ok ]
 * 
 * Space constraints set in the ebuild were not met!
 * The build will most probably fail, you should enhance the space
 * as per failed tests.
 * 
 * ERROR: dev-qt/qtwebengine-5.15.8_p20230313::gentoo failed (pretend phase):
 *   Build requirements not met!
 * 
 * Call stack:
 *                             ebuild.sh, line 136:  Called pkg_pretend
 *   qtwebengine-5.15.8_p20230313.ebuild, line 141:  Called qtwebengine_check-reqs
 *   qtwebengine-5.15.8_p20230313.ebuild, line 137:  Called check-reqs_pkg_pretend
 *                     check-reqs.eclass, line 102:  Called check-reqs_pkg_setup
 *                     check-reqs.eclass, line  93:  Called _check-reqs_output
 *                     check-reqs.eclass, line 300:  Called die
 * The specific snippet of code:
 *              [[ ${EBUILD_PHASE} == "pretend" && -z ${CHECKREQS_DONOTHING} ]] && \
 *                      die "Build requirements not met!"
 * 
 * If you need support, post the output of `emerge --info '=dev-qt/qtwebengine-5.15.8_p20230313::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-qt/qtwebengine-5.15.8_p20230313::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-qt/qtwebengine-5.15.8_p20230313/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebengine-5.15.8_p20230313/temp/die.env'.
 * Working directory: '/var/tmp/portage/dev-qt/qtwebengine-5.15.8_p20230313/empty'
 * S: '/var/tmp/portage/dev-qt/qtwebengine-5.15.8_p20230313/work/qtwebengine-5.15.8_p20230313'

>>> Failed to emerge dev-qt/qtwebengine-5.15.8_p20230313, Log file:

>>>  '/var/tmp/portage/dev-qt/qtwebengine-5.15.8_p20230313/temp/build.log'

>>> Running pre-merge checks for mail-client/thunderbird-102.9.0
 * Checking for at least 6600 MiB disk space at "/var/tmp/portage/mail-client/thunderbird-102.9.0/temp" ...                                                                                                                                                                                  [ ok ]

>>> Running pre-merge checks for www-client/firefox-112.0
 * Checking for at least 13500 MiB disk space at "/var/tmp/portage/www-client/firefox-112.0/temp" ...                                                                                                                                                                                        [ ok ]
Task was destroyed but it is pending!
task: <Task pending name='Task-70' coro=<ForkProcess._proc_join() done, defined at /usr/lib/python3.10/site-packages/portage/util/_async/ForkProcess.py:75> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[_EbuildFetcherProcess._proc_join_done(<Process name...code=-SIGTERM>)()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-71' coro=<PipeLogger._io_loop() done, defined at /usr/lib/python3.10/site-packages/portage/util/_async/PipeLogger.py:85> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[PipeLogger._io_loop_done()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-72' coro=<BuildLogger._main() done, defined at /usr/lib/python3.10/site-packages/portage/util/_async/BuildLogger.py:98> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.10/site-packages/_emerge/AsynchronousTask.py:49, Task.task_wakeup()]> cb=[BuildLogger._main_exit()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-73' coro=<PipeLogger._io_loop() done, defined at /usr/lib/python3.10/site-packages/portage/util/_async/PipeLogger.py:85> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[PipeLogger._io_loop_done()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-74' coro=<SpawnProcess._main() done, defined at /usr/lib/python3.10/site-packages/_emerge/SpawnProcess.py:178> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.10/site-packages/_emerge/AsynchronousTask.py:49, Task.task_wakeup()]> cb=[SpawnProcess._main_exit()]>

[pietinger]

Do I really need to upgrade my ram in order to compile qt-webengine. Does KDE plasma really need 24GiB of free ram in order to compile it?

No ! Your value in MAKEOPTS= (in /etc/portage/make.conf) is too high (-j12). Calculation is: 2 GB x VALUE = 24 GB.
You have two choices:
1. Lower this value, OR
2. Lower this value only for qtwebengine ... described here:
https://wiki.gentoo.org/wiki/User:Pieti ... ckages_.3F

[NeddySeagoon]

<3,

Its real. Big C++ packages want 2G RAM per make thread. That's real RAM.

The ebuild check is

Code: Select all

        # (check-reqs added for bug #570534)
        #
        # Estimate the amount of RAM required
        # Multiplier is *10 because Bash doesn't do floating point maths.
        # Let's crudely assume ~2GB per compiler job for GCC.
        local multiplier=20

        # And call it ~1.5GB for Clang.
        if tc-is-clang ; then
                multiplier=15
        fi

        local CHECKREQS_DISK_BUILD="7G"
        local CHECKREQS_DISK_USR="150M"
        if ! has "distcc" ${FEATURES} ; then
                # bug #830661
                # Not super realistic to come up with good estimates for distcc right now
                local CHECKREQS_MEMORY=$(($(makeopts_jobs)*multiplier/10))G
        fi

With MAKEOPTS="-j12" and gcc in use that's 24G of real RAM. If you feel lucky, the error can be downgraded to a warning. If the build fails, sympathy will be minimal.
That check is trying to save you wasted time.

The right thing to do is to set MAKEOPTS="-j6" or maybe "-j7", not all your RAM is available to gcc, on a per package basis.

[mike155]

Do NOT ask 'Do we really need 24GiB of ram for dev-qt/qtwebengine-5.15.8?'

Do ask: 'Do I need qtwebengine?'

If you don't need it: change a few USE flags - and get rid of it.

[NeddySeagoon]

mike155,

That's the best response to a question I've seen for a long time.
Thank you.

[pietinger]

Do ask: 'Do I need qtwebengine?'

YESSS.

I am a big fan of KDE ... and ... emerge qtwebengine only once and use it in "falkon", "konqueror", "marble", "akregator" - all great applications !

[<3]

Do NOT ask 'Do we really need 24GiB of ram for dev-qt/qtwebengine-5.15.8?'

Do ask: 'Do I need qtwebengine?'

If you don't need it: change a few USE flags - and get rid of it.

Wow, I never even knew that was an option. How come no one ever told me about that? What functionality would be lost by removing it?

[mike155]

The command below returns a list of all packages that depend on qtwebengine:

Code: Select all

equery d qtwebengine

Do you use or need any of those packages?

[flexibeast]

The command below returns a list of all packages that depend on qtwebengine:

Code: Select all

equery d qtwebengine

Note that this won't necessarily show all packages that depend on it; OpenShot depends on qtwebengine, but via PyQtWebEngine, and doesn't get shown in the output of the above command. To show both direct and indirect dependencies, you can add the "-D" option:

Code: Select all

equery d -D qtwebengine

OpenShot's hard dependency on qtwebengine is the only reason i have the latter installed. Recoll, which i also use, has a soft dependency on qtwebengine, but i've set "-webengine" for it.

[Juippisi]

You should be able to skip the check by specifying "CHECKREQS_DONOTHING=1" in package.env, but you may oom out. The check is an estimate.

As others have said, you can lower your MAKEOPTS for qtwebengine with package.env too.

[dmpogo]

Do NOT ask 'Do we really need 24GiB of ram for dev-qt/qtwebengine-5.15.8?'

Do ask: 'Do I need qtwebengine?'

If you don't need it: change a few USE flags - and get rid of it.

Wow, I never even knew that was an option. How come no one ever told me about that? What functionality would be lost by removing it?

I got rid of qtwebengine couple of years ago, and I am KDE user. Yes, I do not use konqueror (never did) or falcon (this one I had to sacrifice), stick with vivaldi-bin and firefox-bin. Compiling browsers is a nightmare nowdays.