Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL: https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL: http://www.chromium.org
Keywords: browser web
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 158
Popularity: 0.004822
First Submitted: 2010-05-17 09:04 (UTC)
Last Updated: 2024-04-21 19:18 (UTC)

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 152 Next › Last »

cmsigler commented on 2017-02-09 17:46 (UTC) (edited on 2017-02-10 17:29 (UTC) by cmsigler)

@sl1pkn07 UPDATE 2: Having researched, this clang build bug is perplexing to me. The clang version d'l'ded for the build is somehow tied into the chromium tree. See src/chromium-58.0.3004.3/tools/clang/scripts/update.py where it says "Do NOT CHANGE this if you don't know what you're doing" and the URL given. But... it's impossible to build chromium with this buggy revision of clang, right? Shouldn't they update clang throughout their own tree? Thank you for answering my comment :) P.S.: I finally spent the time required to verify this hadn't been reported as a chromium bug, then filed a bug report there myself: chromium Issue 690972 Original comment: Hi, For chromium vers. 58.0.3000.4 and 58.0.3004.3 I tried to build with _use_ccache=1 (may not help speed things up very much?) and _use_clang=1. My builds crashed (OneObsession also saw clang failure), in both cases on this file: src/chromium-58.0.3004.3/chrome/common/chrome_content_client.cc. I looked back and I used clang to build ver. 56.0.2897.0 successfully. HTH. UPDATE: This is llvm.org/bugs/ Bug 31043 which is fixed in clang r291064. The clang binary automatically downloaded from Google is clang-289944-2.tgz which hasn't had this bug fixed. Clemmitt

sl1pkn07 commented on 2017-02-08 21:52 (UTC)

Poll: Use GTK3 by default? Remove the PAX related in the PKGBUILD? #discuss

BrettBlackham commented on 2017-02-08 18:14 (UTC)

You should add wget to the list of required packages. Cheers. -> Update libaddressinput strings. -> Update nodejs deps ./third_party/node/update_node_binaries: line 86: wget: command not found ==> ERROR: A failure occurred in prepare(). Aborting...

OneObsession commented on 2017-02-02 19:12 (UTC)

Hi, i was not able to compile chromium with clang. Here is the output: Command '['/tmp/tmpFGCpwT/gn', 'gen', '/home/user/Downloads/chromium-dev/src/chromium-56.0.2924.87/out/Release', '--args=is_debug=false enable_widevine=true enable_hangout_services_extension=false ffmpeg_branding="ChromeOS" proprietary_codecs=true google_api_key="AIzaSyDwr302FpOSkGRpLlUpPThNTDPbXcIn_FM" google_default_client_id="413772536636.apps.googleusercontent.com" google_default_client_secret="0ZChLK6AxeA3Isu96MkwqDR4" fieldtrial_testing_like_official_build=false remove_webcore_debug_symbols=true use_gconf=false use_gio=false use_gnome_keyring=true use_gtk3=false use_pulseaudio=true link_pulseaudio=true use_kerberos=true use_cups=true use_sysroot=false use_gold=false use_allocator="none" linux_use_bundled_binutils=false fatal_linker_warnings=false treat_warnings_as_errors=false enable_nacl=true enable_nacl_nonsfi=true custom_toolchain="/home/user/Downloads/chromium-dev/src:default" is_clang=true clang_use_chrome_plugins=true is_debug=false']' returned non-zero exit status -4

yacuken commented on 2017-01-20 07:52 (UTC)

full build log on pastebin http://pastebin.com/ZrXDhf2X

sl1pkn07 commented on 2017-01-20 06:57 (UTC)

please paste more log, seems is incomplete greetings

yacuken commented on 2017-01-20 06:47 (UTC)

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: /home/yacuken/chromium-dev/src/chromium-57.0.2984.0/out/Release/ Command: python -- /home/yacuken/chromium-dev/src/chromium-57.0.2984.0/build/config/linux/pkg-config.py gmodule-2.0 gtk+-2.0 gthread-2.0 Returned 1. stderr: Package gtk+-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gtk+-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk+-2.0' found Could not run pkg-config. See //build/config/linux/gtk2/BUILD.gn:15:1: whence it was called. pkg_config("gtk2_internal_config") { ^----------------------------------- See //chrome/browser/ui/libgtkui/BUILD.gn:147:12: which caused the file to be included. "//build/config/linux/gtk2", ^--------------------------

sl1pkn07 commented on 2017-01-20 06:46 (UTC)

Please paste the log (for add to the upstream bugreport) Thanks

yacuken commented on 2017-01-20 06:42 (UTC)

gtk2 still needs as makedepends even if use gtk3.

sl1pkn07 commented on 2017-01-16 13:55 (UTC) (edited on 2017-01-16 13:58 (UTC) by sl1pkn07)

try to change the line #168 from gnome-keyring to libgnome-keyring edit: pushed