The chromium-9999 ebuild requires gnome-keyring to be installed as a build dep regardless of whether the gnome-keyring USE flag is set. It will fail before it even starts the build. Reproducible: Always Steps to Reproduce: 1. don't install gnome-keyring 2. emerge chromium 3. watch as bricks are shat Actual Results: bricks are shat Expected Results: chromium hopefully builds? Easy fix, add gnome-keyring to deps, change: gnome-keyring? ( >=gnome-base/gnome-keyring-2.28.2 ) to >=gnome-base/gnome-keyring-2.28.2 PROFIT!
Please post emerge --info and the failure log.
This is all you get. Pretty obvious. Fails right after the svn checkout. Checked out revision 40423. Syncing projects: 100% (57/57), done. ________ running '/usr/bin/python2.6 src/build/gyp_chromium' in '/usr/portage/distfiles/svn-src/chromium' Updating projects from gyp files... Package gnome-keyring-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `gnome-keyring-1.pc' to the PKG_CONFIG_PATH environment variable No package 'gnome-keyring-1' found Traceback (most recent call last): File "src/build/gyp_chromium", line 97, in <module> sys.exit(gyp.main(args)) File "src/tools/gyp/pylib/gyp/__init__.py", line 445, in main options.circular_check) File "src/tools/gyp/pylib/gyp/__init__.py", line 84, in Load depth, generator_input_info, check, circular_check) File "src/tools/gyp/pylib/gyp/input.py", line 2148, in Load depth, check) File "src/tools/gyp/pylib/gyp/input.py", line 422, in LoadTargetBuildFile includes, depth, check) File "src/tools/gyp/pylib/gyp/input.py", line 422, in LoadTargetBuildFile includes, depth, check) File "src/tools/gyp/pylib/gyp/input.py", line 422, in LoadTargetBuildFile includes, depth, check) File "src/tools/gyp/pylib/gyp/input.py", line 380, in LoadTargetBuildFile build_file_path) File "src/tools/gyp/pylib/gyp/input.py", line 967, in ProcessVariablesAndConditionsInDict build_file) File "src/tools/gyp/pylib/gyp/input.py", line 982, in ProcessVariablesAndConditionsInList ProcessVariablesAndConditionsInDict(item, is_late, variables, build_file) File "src/tools/gyp/pylib/gyp/input.py", line 941, in ProcessVariablesAndConditionsInDict ProcessConditionsInDict(the_dict, is_late, variables, build_file) File "src/tools/gyp/pylib/gyp/input.py", line 818, in ProcessConditionsInDict variables, build_file) File "src/tools/gyp/pylib/gyp/input.py", line 960, in ProcessVariablesAndConditionsInDict build_file, key) File "src/tools/gyp/pylib/gyp/input.py", line 967, in ProcessVariablesAndConditionsInDict build_file) File "src/tools/gyp/pylib/gyp/input.py", line 986, in ProcessVariablesAndConditionsInList expanded = ExpandVariables(item, is_late, variables, build_file) File "src/tools/gyp/pylib/gyp/input.py", line 653, in ExpandVariables (contents, p.returncode)) Exception: Call to 'pkg-config --cflags gnome-keyring-1' returned exit status 1. while loading dependencies of src/base/base.gyp while loading dependencies of src/app/app.gyp while loading dependencies of src/build/all.gyp while trying to load src/build/all.gyp Error: /usr/bin/python2.6 src/build/gyp_chromium in /usr/portage/distfiles/svn-src/chromium returned 1 * ERROR: www-client/chromium-9999 failed: * gclient: can't fetch to chromium from http://src.chromium.org/svn/trunk/src/. * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 2861: Called die * The specific snippet of code: * ${EGCLIENT} sync || die "gclient: can't fetch to ${PN} from ${EGCLIENT_REPO_URI}."; * * If you need support, post the output of 'emerge --info =www-client/chromium-9999', * the complete build log and the output of 'emerge -pqv =www-client/chromium-9999'. * The complete build log is located at '/var/tmp/portage/www-client/chromium-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-9999/temp/environment'. * S: '/var/tmp/portage/www-client/chromium-9999/work/chromium-9999' >>> Failed to emerge www-client/chromium-9999, Log file: >>> '/var/tmp/portage/www-client/chromium-9999/temp/build.log' * Messages for package www-client/chromium-9999: * ERROR: www-client/chromium-9999 failed: * gclient: can't fetch to chromium from http://src.chromium.org/svn/trunk/src/. * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 2861: Called die * The specific snippet of code: * ${EGCLIENT} sync || die "gclient: can't fetch to ${PN} from ${EGCLIENT_REPO_URI}."; * * If you need support, post the output of 'emerge --info =www-client/chromium-9999', * the complete build log and the output of 'emerge -pqv =www-client/chromium-9999'. * The complete build log is located at '/var/tmp/portage/www-client/chromium-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-9999/temp/environment'. * S: '/var/tmp/portage/www-client/chromium-9999/work/chromium-9999'
Created attachment 247749 [details] gnome-keyring patch log Failed to apply chromium-gnome-keyring-r0.patch. may or may not be related.
Just for record keeping. And now for the non-gnome users..... not having any gnome infra. Or this is package is just another one to drop. (forme).
Chromium still need gnomekeyring [ebuild N ] gnome-base/gnome-keyring-2.30.3 USE="pam -debug -doc -test" 1,556 kB [ebuild N ] gnome-base/libgnome-keyring-2.30.1 USE="-debug -doc -test" 794 kB [ebuild N ] www-client/chromium-6.0.472.59-r1 USE="sse2 -cups -gnome-keyring" 121,083 kB
This is probably happening because gyp_chromium is called implicitly by the a gclient hook in src/DEPS. When this happens, use_gnome_keyring has its default value (1), so the pkgconfig logic in src/build/system.gyp gets called. The subsequent call to gyp_chromium in src_configure() sets use_gnome_keyring=0, so the pkgconfig logic will be avoided. Calling "gclient sync --nohooks" will prevent the extraneous call to gyp_chromium.
Correction: The pkg-config call is in "src/build/linux/system.gyp".
chromium-gnome-keyring-r0.patch no longer applies on -9999, it seems to have been merged upstream (I can compile it without gnome-keyring installed now)
(In reply to comment #8) > chromium-gnome-keyring-r0.patch no longer applies on -9999, it seems to have > been merged upstream (I can compile it without gnome-keyring installed now) Thanks, fixed. Please reopen if there are further problems.
