Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 599340 - www-client/chromium-56.0.2906.0 requires gtk3
Summary: www-client/chromium-56.0.2906.0 requires gtk3
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Chromium Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-09 20:17 UTC by Joe Kappus
Modified: 2016-11-09 23:59 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Kappus 2016-11-09 20:17:21 UTC
Summary:

Build fails on chromium configuration. Even without gnome and gnome-keyring useflags. Previously could build without GTK3 being present on system.



Useflags:

USE="cups custom-cflags hangouts (pic) proprietary-codecs suid system-ffmpeg tcmalloc widevine -gnome -gnome-keyring (-gtk3) -kerberos (-neon) -pulseaudio (-selinux) {-test}"


Error: 

DEBUG:root:Running: /var/tmp/portage/www-client/chromium-56.0.2906.0/work/temp/tmplhDxZC/gn gen /var/tmp/portage/www-client/chromium-56.0.2906.0/work/chromium-56.0.2906.0/out/Release --args= is_debug=false enable_nacl=false enable_hangout_services_extension=true enable_widevine=true use_cups=true use_gconf=false use_gnome_keyring=false use_gtk3=false use_kerberos=false use_pulseaudio=false fieldtrial_testing_like_official_build=true is_clang=false use_gold=false use_sysroot=false linux_use_bundled_binutils=false proprietary_codecs=true ffmpeg_branding="Chrome" google_api_key="AIzaSyDEAOvatFo0eTgsV_ZlEzx0ObmepsMzfAc" google_default_client_id="329227923882.apps.googleusercontent.com" google_default_client_secret="vgKG0NNv7GoDpbtoFNLxCUXu" treat_warnings_as_errors=false fatal_linker_warnings=false custom_toolchain="/usr/portage/www-client/chromium/files/toolchain:default" use_allocator="none" is_debug=false
ERROR at //build/config/linux/pkg_config.gni:85:17: Script returned non-zero exit code.
    pkgresult = exec_script(pkg_config_script, args, "value")
                ^----------
Current dir: /var/tmp/portage/www-client/chromium-56.0.2906.0/work/chromium-56.0.2906.0/out/Release/
Command: python -- /var/tmp/portage/www-client/chromium-56.0.2906.0/work/chromium-56.0.2906.0/build/config/linux/pkg-config.py gmodule-2.0 gtk+-3.0 gthread-2.0
Returned 1.
stderr:

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

See //build/config/linux/gtk3/BUILD.gn:14:1: whence it was called.
pkg_config("gtk3_internal_config") {
^-----------------------------------
See //chrome/browser/ui/libgtkui/BUILD.gn:143:12: which caused the file to be included.
           "//build/config/linux/gtk3",
           ^--------------------------
Command '['/var/tmp/portage/www-client/chromium-56.0.2906.0/work/temp/tmplhDxZC/gn', 'gen', '/var/tmp/portage/www-client/chromium-56.0.2906.0/work/chromium-56.0.2906.0/out/Release', '--args= is_debug=false enable_nacl=false enable_hangout_services_extension=true enable_widevine=true use_cups=true use_gconf=false use_gnome_keyring=false use_gtk3=false use_kerberos=false use_pulseaudio=false fieldtrial_testing_like_official_build=true is_clang=false use_gold=false use_sysroot=false linux_use_bundled_binutils=false proprietary_codecs=true ffmpeg_branding="Chrome" google_api_key="AIzaSyDEAOvatFo0eTgsV_ZlEzx0ObmepsMzfAc" google_default_client_id="329227923882.apps.googleusercontent.com" google_default_client_secret="vgKG0NNv7GoDpbtoFNLxCUXu" treat_warnings_as_errors=false fatal_linker_warnings=false custom_toolchain="/usr/portage/www-client/chromium/files/toolchain:default" use_allocator="none" is_debug=false']' returned non-zero exit status 1
Comment 1 Dirk Pranke 2016-11-09 23:11:26 UTC
Yes, we've recently changed things in Chromium so that we build in support for gtk3 by default (when you build everything). Chrome itself does not require it.

The `use_gtk3` flag at the moment is false and determines whether or not Chrome will link against it. There is not currently a way to disable the compile-time requirement, unless you want to build with ozone instead.

We can add one but I wouldn't necessarily want to do that without understanding whether we can just add the compile-time headers instead.

(Obviously, compile-time and run-time dependencies are two different things).
Comment 2 Mike Gilbert gentoo-dev 2016-11-09 23:59:43 UTC
commit a382a8fb0c8f23b6e299ee86d8d13122b3c05dae
Author: Mike Gilbert <floppym@gentoo.org>
Date:   Wed Nov 9 18:58:41 2016 -0500

    www-client/chromium: depend on both gtk2 and gtk3 at build time
    
    Bug: https://bugs.gentoo.org/599340
    Package-Manager: portage-2.3.2_p5

 www-client/chromium/chromium-56.0.2906.0.ebuild | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)