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.005340
First Submitted: 2010-05-17 09:04 (UTC)
Last Updated: 2024-04-21 19:18 (UTC)

Dependencies (84)

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 97 98 99 100 101 102 103 104 105 106 107 .. 152 Next › Last »

wuffleton commented on 2012-05-12 17:37 (UTC)

20.0.1132.3-1's compile succeeded for me, but I noticed that the .pacnew file for /etc/default didn't work. When I removed the flags relating to pepper-flash (the new default is blank), it was not detected by chromium. Regarding the compile issue: I do not have this file either, but it compiled just fine on my box.

imrehg commented on 2012-05-12 16:17 (UTC)

compilaton of 20.0.1132.3-1 fails with: In file included from ./remoting/protocol/authentication_method.h:16:0, from remoting/protocol/authentication_method.cc:5: /usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.0/../../../../include/c++/4.7.0/string:45:69: fatal error: /usr/include/cairo/bits/localefwd.h: Permission denied compilation terminated. make: *** [out/Release/obj.target/remoting_protocol/remoting/protocol/authentication_method.o] Error 1 Actually, the file /usr/include/cairo/bits/localefwd.h does not exists in my system, is that a missing dependency? What would it be?

sl1pkn07 commented on 2012-05-09 16:28 (UTC)

with new compilation (rev2) fails for me :S

sl1pkn07 commented on 2012-05-09 15:11 (UTC)

oh! i see. yes i'm use the raw patch (http://chromium.googlecode.com/issues/attachment?aid=1225250019000&name=sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch&token=jqQlLFZFmSnbOxt60rCB6H5mAIo%3A1336575820598) oks. update pkgbuild to v2 sorry the inconvenient :S

wuffleton commented on 2012-05-09 14:41 (UTC)

Looks like you're using the raw patch (which came directly from sqlite) you need to patch third_party/sqlite/amalgamation/sqlite3.c in order for it to be included in the build. It was mentioned on the bug report comments and the new chromium PKGBUILD does this. The edited patch I posted earlier is pointed at that file (or you could just do what the PKGBUILD in extra is doing). Things have been stable for me with this patch included.

sl1pkn07 commented on 2012-05-09 13:03 (UTC)

i think is my faul to apply sqlite patch. i'm test new pkgbuild with chages like chromium package from extra please patient

sl1pkn07 commented on 2012-05-09 12:46 (UTC)

ag! still fails :S

wuffleton commented on 2012-05-09 02:01 (UTC)

Just a heads up, a patch that fixes the segfaults was posted on the bug report page ( http://crbug.com/122525 ). I edited the patch since a later comment indicated that the patch needed to be used on a different file in order to be included in the build. You can get that patch here: http://dl.dropbox.com/u/6464618/sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch Then just add this to the PKGBUILD and you're good to go: patch --silent -Np0 -i "${srcdir}"/sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch Also, 20.0.1130.1 is out according to the RPM list.

fishburn commented on 2012-05-07 15:23 (UTC)

That's strange that I'm the only one having the problem. After searching /usr/lib for *expat* before and after installing pyxml, it looks like: /usr/lib/python2.7/lib-dynload/pyexpat.so is superseded by: /usr/lib/python2.7/site-packages/_xmlplus/parsers/pyexpat.so If I rename the new pyexpat.so, the same error returns. I have no idea how this arose, but reinstalling all of the relevant packages didn't change anything. Its not a big problem since its working now, but it is strange.

jeagoss commented on 2012-05-07 08:46 (UTC)

I definitely don't have pyxml installed, and chromium-dev compiles for me every time. It seems there might have been some kind of install problem that the installation of pyxml might have repaired.