Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 936673 - www-client/chromium-127.0.6533.72 fails to compile
Summary: www-client/chromium-127.0.6533.72 fails to compile
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal major
Assignee: Chromium Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-26 17:06 UTC by Alex Buell
Modified: 2024-08-02 06:00 UTC (History)
10 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log.gz,2.29 KB, application/gzip)
2024-07-26 17:15 UTC, Alex Buell
Details
emerge --info (info.log,7.13 KB, text/x-log)
2024-07-26 17:16 UTC, Alex Buell
Details
build.log after the fix with -official (build_unofficial.log,7.66 KB, text/x-log)
2024-07-28 17:35 UTC, Simeon Simeonov
Details
build.log (build.log,7.32 KB, text/plain)
2024-07-29 18:16 UTC, John J. Aylward
Details
build.log after the latest fix (build_unofficial2.log,7.77 KB, text/x-log)
2024-07-30 05:46 UTC, Simeon Simeonov
Details
build.log (build.log,7.77 KB, text/x-log)
2024-07-31 08:49 UTC, Jana Jarosu
Details
environment (environment,213.70 KB, text/plain)
2024-07-31 09:01 UTC, Jana Jarosu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Buell 2024-07-26 17:06:22 UTC
Chromium fails to complete the configuration phase with an error:



Reproducible: Always
Comment 1 Alex Buell 2024-07-26 17:15:30 UTC
Created attachment 898379 [details]
build.log
Comment 2 Alex Buell 2024-07-26 17:16:40 UTC
Created attachment 898380 [details]
emerge --info
Comment 3 Alex Buell 2024-07-26 17:17:17 UTC
(In reply to Alex Buell from comment #0)
> Chromium fails to complete the configuration phase with an error:
> 
> 
> 
> Reproducible: Always

ERROR at //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
    pkgresult = exec_script(pkg_config_script, args, "json")
                ^----------
Current dir: /var/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72/out/Release/
Command: python3.11 /var/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72/build/config/linux/pkg-config.py libsystemd
Returned 1.
stderr:

Package libsystemd was not found in the pkg-config search path.
Perhaps you should add the directory containing `libsystemd.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libsystemd' not found
Could not run pkg-config.
Comment 4 Alex Buell 2024-07-26 17:17:47 UTC
I do not use systemd, only OpenRC.
Comment 5 yknot 2024-07-26 18:50:48 UTC
I use OpenRC on my gentoo system

profile amd64/23.0/desktop/plasma

chromium-127.0.6533.72 fails to compile with
"Package libsystemd was not found in the pkg-config search path"
Comment 6 5836000 2024-07-27 03:27:32 UTC
same error
Comment 7 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-07-28 01:55:23 UTC
In the past, there was https://github.com/chromium/chromium/commit/758ad0a60a0b07df75f5523508297d03b540fc8d.

I see https://chromium.googlesource.com/chromium/src/+/HEAD/chrome/browser/buildflags.gni#10, i.e. maybe enable_updater=false will work, but it's just enabled by default for official builds.
Comment 8 Larry the Git Cow gentoo-dev 2024-07-28 09:35:16 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2b96b04ef3d7b876ccf29de8ee1738f49112c95f

commit 2b96b04ef3d7b876ccf29de8ee1738f49112c95f
Author:     Matt Jolly <kangie@gentoo.org>
AuthorDate: 2024-07-28 09:34:19 +0000
Commit:     Matt Jolly <kangie@gentoo.org>
CommitDate: 2024-07-28 09:35:05 +0000

    www-client/chromium: forcibly disable 'updater' target for 127
    
    Closes: https://bugs.gentoo.org/936673
    Signed-off-by: Matt Jolly <kangie@gentoo.org>

 www-client/chromium/chromium-127.0.6533.72.ebuild | 5 +++++
 1 file changed, 5 insertions(+)
Comment 9 Matt Jolly gentoo-dev 2024-07-28 09:36:24 UTC
I'm not sure why this was happening but forcibly disabling the updater in GN seems to do the trick. Let's proceed with that for now.

Closed because my testing successfully passes configure in an OpenRC chroot. Please let me know if you have any further issues!
Comment 10 Simeon Simeonov 2024-07-28 17:32:34 UTC
I have the same issue when building with -official (on OpenRC system).
Comment 11 Simeon Simeonov 2024-07-28 17:35:35 UTC
Created attachment 898471 [details]
build.log after the fix with -official

build.log after the fix with -official
Comment 12 Matt Jolly gentoo-dev 2024-07-28 23:58:30 UTC
Hi Simeon,

Just confirming that you're still seeing this issue even with the latest ebuild update and that it seems to be related to toggling USE=official?
Comment 13 Matt Jolly gentoo-dev 2024-07-28 23:59:19 UTC
Should have checked your build log! I'll reopen the ticket and see if I can reproduce.
Comment 14 Alex Buell 2024-07-29 07:38:06 UTC
Yes this fixes my issue completely, thank you.

I reported a separate issue with sys-devel/mold last night with this version.
Comment 15 John J. Aylward 2024-07-29 18:11:13 UTC
I am still experiencing this after the latest patch. It now fails at

Current dir: /var/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72/out/Release/
Command: python3.12 /var/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72/build/config/linux/pkg-config.py libsystemd
Returned 1.
stderr:

Package libsystemd was not found in the pkg-config search path.
Perhaps you should add the directory containing `libsystemd.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libsystemd' not found
Could not run pkg-config.

See //chrome/updater/linux/BUILD.gn:20:1: whence it was called.
pkg_config("libsystemd") {
^-------------------------
See //chrome/updater/BUILD.gn:25:14: which caused the file to be included.
    deps = [ "//chrome/updater/linux" ]



current USE flags:

[ebuild     U  ] www-client/chromium-127.0.6533.72:0/stable::gentoo [126.0.6478.182:0/stable::gentoo] USE="cups hangouts lto* proprietary-codecs pulseaudio qt5 qt6 screencast system-harfbuzz system-icu system-png system-toolchain system-zstd vaapi wayland widevine -X* -bindist -custom-cflags -debug -ffmpeg-chromium -gtk4 (-headless) -kerberos -official* -pax-kernel (-pgo) (-selinux) (-libcxx%)" L10N="es fr ja* ko* -af -am -ar -bg -bn -ca -cs -da -de -el -en-GB -es-419 -et -fa -fi -fil -gu -he -hi -hr -hu -id -it -kn -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -ur -vi -zh-CN -zh-TW"
Comment 16 John J. Aylward 2024-07-29 18:16:07 UTC
Created attachment 898592 [details]
build.log
Comment 17 Larry the Git Cow gentoo-dev 2024-07-29 22:43:54 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea8d28aa98aee00aafd19a81032dc6c9cde530c5

commit ea8d28aa98aee00aafd19a81032dc6c9cde530c5
Author:     Matt Jolly <kangie@gentoo.org>
AuthorDate: 2024-07-29 22:41:57 +0000
Commit:     Matt Jolly <kangie@gentoo.org>
CommitDate: 2024-07-29 22:43:42 +0000

    www-client/chromium: fix build with USE="-official" on OpenRC
    
    Closes: https://bugs.gentoo.org/936673
    Signed-off-by: Matt Jolly <kangie@gentoo.org>

 www-client/chromium/chromium-127.0.6533.72.ebuild  |  1 +
 .../files/chromium-127-enterprise-companion.patch  | 44 ++++++++++++++++++++++
 2 files changed, 45 insertions(+)
Comment 18 Matt Jolly gentoo-dev 2024-07-29 22:45:06 UTC
I tracked this one down yesterday to a new component that is _only_ enabled when USE=official/is_official_build is set to false.

The new patch should resolve that issue. Please let me know how you go!
Comment 19 Simeon Simeonov 2024-07-30 05:45:24 UTC
I get the same error, unfortunately. (build.log attached)
Comment 20 Simeon Simeonov 2024-07-30 05:46:48 UTC
Created attachment 898612 [details]
build.log after the latest fix

build.log for -official
Comment 21 Stefano 2024-07-30 09:46:40 UTC
For me the fix closed the issue, thanks
Comment 22 Jana Jarosu 2024-07-31 08:47:19 UTC
I still have the problem...

ERROR at //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
    pkgresult = exec_script(pkg_config_script, args, "json")
                ^----------
Current dir: /home/portage/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72/out/Release/
Command: python3.11 /home/portage/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72/build/config/linux/pkg-config.py libsystemd
Returned 1.
stderr:

Package libsystemd was not found in the pkg-config search path.
Perhaps you should add the directory containing `libsystemd.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libsystemd' not found
Could not run pkg-config.

See //chrome/updater/linux/BUILD.gn:20:1: whence it was called.
pkg_config("libsystemd") {
^-------------------------
See //chrome/updater/BUILD.gn:25:14: which caused the file to be included.
    deps = [ "//chrome/updater/linux" ]
             ^-----------------------
 * ERROR: www-client/chromium-127.0.6533.72::gentoo failed (configure phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  136:  Called src_configure
 *   environment, line 4733:  Called chromium_configure '0'
 *   environment, line 1964:  Called die
 * The specific snippet of code:
 *       "$@" || die
 * 
 * If you need support, post the output of `emerge --info '=www-client/chromium-127.0.6533.72::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=www-client/chromium-127.0.6533.72::gentoo'`.
 * The complete build log is located at '/home/portage/tmp/portage/www-client/chromium-127.0.6533.72/temp/build.log'.
 * The ebuild environment file is located at '/home/portage/tmp/portage/www-client/chromium-127.0.6533.72/temp/environment'.
 * Working directory: '/home/portage/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72'
 * S: '/home/portage/tmp/portage/www-client/chromium-127.0.6533.72/work/chromium-127.0.6533.72'
j
Comment 23 Jana Jarosu 2024-07-31 08:49:35 UTC
Created attachment 898698 [details]
build.log

Current build.log, USE="-official"
Comment 24 Jana Jarosu 2024-07-31 09:01:55 UTC
Created attachment 898699 [details]
environment

It's behaving strangely, USE="-official" looks different in "emerge -av1 chromium" and different in environment.log. It is disabled here:

-----------------------------------
~ # emerge -av1 chromium

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 8.14 s (backtrack: 0/20).

[ebuild     U  ] www-client/chromium-127.0.6533.72:0/stable::gentoo [126.0.6478.182:0/stable::gentoo] USE="X cups proprietary-codecs pulseaudio qt5 screencast system-icu system-toolchain system-zstd vaapi wayland widevine -bindist -custom-cflags -debug -ffmpeg-chromium -gtk4 -hangouts (-headless) -kerberos -lto -official -pax-kernel (-pgo) -qt6 (-selinux) -system-harfbuzz -system-png (-libcxx%)" L10N="cs -af -am -ar -bg -bn -ca -da -de -el -en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -ur -vi -zh-CN -zh-TW" 0 KiB

Total: 1 package (1 upgrade), Size of downloads: 0 KiB
-----------------------------------

And it's allowed here:
-----------------------------------
~ # grep IUSE_EFFECTIVE /home/portage/tmp/portage/www-client/chromium-127.0.6533.72/temp/environment 
declare -x IUSE_EFFECTIVE="X abi_x86_64 alpha amd64 amd64-linux arm arm64 arm64-macos bindist cups custom-cflags debug elibc_Darwin elibc_SunOS elibc_bionic elibc_glibc elibc_mingw elibc_musl ffmpeg-chromium gtk4 hangouts headless hppa ia64 kerberos kernel_Darwin kernel_SunOS kernel_linux l10n_af l10n_am l10n_ar l10n_bg l10n_bn l10n_ca l10n_cs l10n_da l10n_de l10n_el l10n_en-GB l10n_es l10n_es-419 l10n_et l10n_fa l10n_fi l10n_fil l10n_fr l10n_gu l10n_he l10n_hi l10n_hr l10n_hu l10n_id l10n_it l10n_ja l10n_kn l10n_ko l10n_lt l10n_lv l10n_ml l10n_mr l10n_ms l10n_nb l10n_nl l10n_pl l10n_pt-BR l10n_pt-PT l10n_ro l10n_ru l10n_sk l10n_sl l10n_sr l10n_sv l10n_sw l10n_ta l10n_te l10n_th l10n_tr l10n_uk l10n_ur l10n_vi l10n_zh-CN l10n_zh-TW loong lto m68k mips official pax-kernel pgo ppc ppc-macos ppc64 ppc64-linux prefix prefix-guest prefix-stack proprietary-codecs pulseaudio qt5 qt6 riscv s390 screencast selinux sparc system-harfbuzz system-icu system-png system-toolchain system-zstd vaapi wayland widevine x64-macos x64-solaris x86 x86-linux"
    local liuse=(${IUSE_EFFECTIVE});
-----------------------------------
Comment 25 Jana Jarosu 2024-07-31 09:12:52 UTC
Sorry, I misunderstood, after switching to USE="lto official" it goes through...
Comment 26 Matt Jolly gentoo-dev 2024-07-31 13:47:42 UTC
Yes the "official" flag masks the issue. We have a better fix in the works for this week's bump.
Comment 27 John J. Aylward 2024-07-31 16:43:26 UTC
I still have the issue with -official
Comment 28 Larry the Git Cow gentoo-dev 2024-08-01 08:40:01 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e52b059766917ec7c3d0c1af5ea377e82c9529c3

commit e52b059766917ec7c3d0c1af5ea377e82c9529c3
Author:     Matt Jolly <kangie@gentoo.org>
AuthorDate: 2024-08-01 06:49:05 +0000
Commit:     Matt Jolly <kangie@gentoo.org>
CommitDate: 2024-08-01 08:39:11 +0000

    www-client/chromium: add 127.0.6533.88
    
    Also drop LTO use in favour of `tc-is-lto`
    
    Closes: https://bugs.gentoo.org/937025
    Closes: https://bugs.gentoo.org/936959
    Bug: https://bugs.gentoo.org/936673
    Signed-off-by: Matt Jolly <kangie@gentoo.org>

 www-client/chromium/Manifest                       |    2 +
 www-client/chromium/chromium-127.0.6533.88.ebuild  | 1443 ++++++++++++++++++++
 .../files/chromium-127-updater-systemd.patch       |   73 +
 3 files changed, 1518 insertions(+)
Comment 29 Simeon Simeonov 2024-08-02 06:00:37 UTC
127.0.6533.88 now builds fine with -official