Summary: | dev-qt/qtwebengine-5.15.5_p20220618 ignores MAKEOPTS (when resuming with FEATURE="keepwork") | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vadim Voelk <fuer_das_volk> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | UNCONFIRMED --- | ||
Severity: | minor | CC: | gyakovlev, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 654178 | ||
Attachments: |
failing to compile after resuming with FEATURE="keepwork"
"ps aux" when resuming compiling qtwebengine with FEATURE="keepwork". In this case MAKEOPTS are ignored |
Description
Vadim Voelk
2022-07-04 14:53:52 UTC
1. Could you grab `ps aux` output when it's acting badly (without your change)? 2. What is NINJAFLAGS when it's acting badly? 3. I wonder if it's just wrong as-is, given: ``` commit a00223eb88742885325b8863ba080e7d94202d8f Author: Michał Górny <mgorny@gentoo.org> Date: Thu Apr 28 12:44:02 2022 +0200 multiprocessing.eclass: Default makeopts_jobs to inf=nproc+1 Change the default value for 'inf' argument to makeopts_jobs from 999 to $(get_nproc) + 1. This means that if MAKEOPTS specifies a `-j` argument without a specific value, nproc will be used rather than infinity-ish number of jobs. The old default made sense for ebuilds using both makeopts_jobs and makeopts_loadavg. However, these are very rare — only 4 packages and 3 eclass at this time. For the remaining ebuilds, they meant uncontrollably using up to 999 jobs. The new default is both safer and more correct for the vast majority of Gentoo packages, removing the necessity of repeating: $(makeopts_jobs "${MAKEOPTS}" "$(get_nproc)") The ebuilds and eclasses using makeopts_loadavg have been updated to pass the old default. Signed-off-by: Michał Górny <mgorny@gentoo.org> ``` but I thought we'd cleaned up all the ebuild uses of this. Created attachment 791339 [details]
failing to compile after resuming with FEATURE="keepwork"
Well my bad, the issues appears only if I continue to compile with FEATURE="keepwork". As I previously mentioned, python command points to "/var/tmp/portage/dev-qt/qtwebengine-5.15.5_p20220618/temp/python3.10/bin/python" instead something like "/usr/bin/python3.10" After I have changed this in these files: /var/tmp/portage/dev-qt/qtwebengine-5.15.5_p20220618/work/qtwebengine-5.15.5_p20220618_build/src/core/release/host/toolchain.ninja /var/tmp/portage/dev-qt/qtwebengine-5.15.5_p20220618/work/qtwebengine-5.15.5_p20220618_build/src/core/release/build.ninja /var/tmp/portage/dev-qt/qtwebengine-5.15.5_p20220618/work/qtwebengine-5.15.5_p20220618_build/src/buildtools/qtbuildtools-config.pri I was able to continue to compile. And at this stage, MAKEOPTS are ignored. Also I don't know how to display NINJAFLAGS when resuming compilation. I tried "echo" it in section "pkg_setup()" in this ebuild, but it seems it's never called. P.S.: Chromium itself compiles fine with FEATURE="keepwork", though probably even longer than qtwebengine Created attachment 791342 [details]
"ps aux" when resuming compiling qtwebengine with FEATURE="keepwork". In this case MAKEOPTS are ignored
You're saying "ignored". Do you mean you change them mid compile then resume with keepwork? That won't work as it's saved in the environment file. (In reply to Sam James from comment #5) > You're saying "ignored". Do you mean you change them mid compile then resume > with keepwork? That won't work as it's saved in the environment file. I suppose in this case it gets forgotten. Because I did start compiling with 2 jobs, but when I resume (with keepwork) it's not 2 anymore. |