Package Details: chromium-dev 58.0.3013.3-1

Git Clone URL: (read-only)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL:
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 147
Popularity: 0.095798
First Submitted: 2010-05-17 09:04
Last Updated: 2017-02-19 14:56

Dependencies (37)

Required by (3)

Sources (12)

Pinned Comments

sl1pkn07 commented on 2017-02-08 21:52


Use GTK3 by default?
Remove the PAX related in the PKGBUILD?


Latest Comments

misc commented on 2017-02-20 14:32

Video is completely broken from me in this version.

LordAro commented on 2017-02-15 00:04

Looks great, ta (I think I only had trouble with python & node, but all 3 works as well)

sl1pkn07 commented on 2017-02-14 23:36

oh. i see


LordAro commented on 2017-02-14 23:12

Can you add a couple of -f to the ln commands? Getting "failed to create symbolic link" every time I try to rebuild this is a bit boring...

digitalone commented on 2017-02-13 21:53

Can someone upload a binary package with vaapi patch? Thanks.

cmsigler commented on 2017-02-11 13:56

One final update on building with (chromium's version of) clang -- See chromium Issue 685244,

This issue was filed Jan 25th by a project member. It's a request to "roll clang again," meaning to update the version of clang packaged with/in the chromium tree.

OT: Their bug tracker is insane! I have no idea how anything ever gets fixed. A quick glance shows they have 150-200 issues filed *every*24*hours*! I hope a senior project member filed the clang bug. Otherwise, no one will ever notice it :(


sl1pkn07 commented on 2017-02-09 19:47

for tht i back to gcc (see the commit log)

cmsigler commented on 2017-02-09 17:46

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/ 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:

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/

I looked back and I used clang to build ver. 56.0.2897.0 successfully. HTH.

UPDATE: This is 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.


sl1pkn07 commented on 2017-02-08 21:52


Use GTK3 by default?
Remove the PAX related in the PKGBUILD?


BrettBlackham commented on 2017-02-08 18:14

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().

All comments