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.004725
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 .. 112 113 114 115 116 117 118 119 120 121 122 .. 152 Next › Last »

sl1pkn07 commented on 2012-01-11 11:58 (UTC)

update to 18.0.1003.1 fixed: http://crbug.com/104569 (no need patch anymore) http://crbug.com/108228 (fixed in 18.) @darksniper http://crbug.com/106954 (no need patch anymore) back mv instead cp -R add exception for "third_party/libyuv/" (thanks @imrehg) remove Debug code greetings

wuffleton commented on 2012-01-08 21:09 (UTC)

That was exactly the issue, built fine [without eating up loads of space] after changing that =D However, it seems that this version still contains this bug, whereas the latest stable one fixed it: http://crbug.com/108228

sl1pkn07 commented on 2012-01-07 21:33 (UTC)

try this: in build() mv instead cp -R only source code need 852MiB

wuffleton commented on 2012-01-07 16:15 (UTC)

Just wondering... Is it just me, or does building chromium now take an outrageous amount of disk space? On earlier builds I was able to build the whole thing in my 2GB tmpfs, now I can't even extract the source without running out of space. For some odd reason, the source alone it's taking up about 700 megs more on /tmp than it does on my hard drive, and I'm pretty sure that BTRFS's compression isn't responsible for such a big difference in size. I bumped /tmp's size up to 2.5 gigs and it barely got to the end of the NACL SDK thing before running out of space again. Any ideas on what might be causing this?

imrehg commented on 2012-01-02 11:22 (UTC)

For newer versions I had to add an exception for "third_party/libyuv/" in the "Remove unnecesary components" section, otherwise the build breaks. With this small change (and disabling nacl) I could successfully build 18.0.993.0 By the way, is that section really necessary? Can't the build system decide what it needs the build and what not? It took a while to track down while a build breaks with "missing header file", when it is originally there.

sl1pkn07 commented on 2011-12-28 14:50 (UTC)

install with yaourt. its more easy yaourt -Sa nameofpackage or with edit /etc/yaourtrc AURSEARCH=1 , install with simply yaourt -S nameofpackage whist this install all necesary dependencies in all packages example this: yaourt -S chromium-dev https://wiki.archlinux.org/index.php/Yaourt

darnir commented on 2011-12-28 11:27 (UTC)

Okay, my mistake. I had only made the package, not installed it. Still new to Arch, figuring my way out.. Once I ran makepkg -si, it installed libwebp, and no problem thence. Though, shouldnt that be automated when I run makepkg -si for the chromium-dev package?

sl1pkn07 commented on 2011-12-28 10:43 (UTC)

are you sure install libwebp?. try install with yaourt (yaourt -Sa libwebp)

darnir commented on 2011-12-28 08:04 (UTC)

While installing, I ran makepkg -s, and got an error: error: target not found: libwebp => Error: 'pacman' failed to install missing dependencies. So, I followed the link to the libwebp package and manually installed it. Yet I keep getting this error and cannot install the chromium-dev package.

sl1pkn07 commented on 2011-12-16 19:56 (UTC)

@oraerk in compile time. buid 64 and 32bits plugin in same time

« First ‹ Previous 1 .. 112 113 114 115 116 117 118 119 120 121 122 .. 152 Next › Last »