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: 160
Popularity: 0.010679
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 .. 128 129 130 131 132 133 134 135 136 137 138 .. 152 Next › Last »

<deleted-account> commented on 2011-02-01 14:42 (UTC)

There was no .11 tarball so I packaged .12. @Det: "next update" = "when I have time".

Det commented on 2011-02-01 13:55 (UTC)

Out of curiosity, is there a specific reason you want to wait until the next release each time there's something to be changed in the PKGBUILD? If you checked/verified that (10.0.648).11 was already released, then it's of course fine to just say that you'll be doing both changes on the same go, though.

<deleted-account> commented on 2011-02-01 13:21 (UTC)

lastchange.py uses git, I'll add it to makedepends in the next update.

terminalmage commented on 2011-01-31 19:36 (UTC)

I have the same error when building on i686, only with out/Release/obj.target/geni/webkit_version.h instead of out/Release/obj/gen/chrome/grit/component_extension_resources.h. Didn't have a problem building on x86_64 though.

obbala commented on 2011-01-31 06:59 (UTC)

...fails to compile... RULE chrome_extra_resources_grit_0 out/Release/obj/gen/chrome/grit/component_extension_resources.h Traceback (most recent call last): File "./lastchange.py", line 149, in <module> sys.exit(main()) File "./lastchange.py", line 134, in main version_info = FetchVersionInfo(opts.default_lastchange) File "./lastchange.py", line 84, in FetchVersionInfo if IsGitSVN(directory): File "./lastchange.py", line 31, in IsGitSVN cwd=directory) File "/usr/lib/python2.7/subprocess.py", line 486, in call return Popen(*popenargs, **kwargs).wait() File "/usr/lib/python2.7/subprocess.py", line 672, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1202, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory make: *** [out/Release/obj/gen/build/LASTCHANGE.always] Fehler 1 make: *** Warte auf noch nicht beendete Prozesse... WARNING - duplicate keys exist in shortcut group IDD_CHROME_FRAME_FIND_DIALOG sk duplicates: &N fr duplicates: &R ro duplicates: &G nl duplicates: &O no duplicates: &N pt-PT duplicates: &P sw duplicates: &F ca duplicates: &A de duplicates: &N tr duplicates: &A sv duplicates: &S da duplicates: &O lv duplicates: &R, &U pl duplicates: &W cs duplicates: &N fi duplicates: &K es-419 duplicates: &A id duplicates: &T es duplicates: &B

<deleted-account> commented on 2011-01-25 08:23 (UTC)

I've also tried to compile without 'disable_sse2=1' on x86_64 Intel Core 2 Duo, Intel Core i5, Intel Xeon. Everything seems to work fine.

<deleted-account> commented on 2011-01-15 07:06 (UTC)

OK, I'll add this in the next update.

Vi0L0 commented on 2011-01-14 17:54 (UTC)

i've compiled it on x86_64 with sse2 and everything is ok - so i could recommend it to other x86_64 users. ofcourse you can leave it how it looks now - if somebody wants he can always remove 'disable_sse2=1' but maybe a good consensus here is to copy solution from [1] extra's chromium: $([ "${CARCH}" == 'i686' ] && echo '-Ddisable_sse2=1') [1] http://projects.archlinux.org/svntogit/packages.git/tree/chromium/repos/extra-x86_64/PKGBUILD

<deleted-account> commented on 2011-01-14 16:08 (UTC)

It seems that enabling SSE2 results in wrong CFLAGS on some systems: http://bugs.gentoo.org/show_bug.cgi?id=336871 At least it is forcibly disabled in Gentoo for that reason: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/chromium-10.0.634.0.ebuild?revision=1.1&view=markup

Vi0L0 commented on 2011-01-14 15:41 (UTC)

hmm... i can only see disable_sse2=1 and afaik sse2 is supported by all x86_64 cpus - so we don't need any check for this arch ofcourse if im right, but i should be - sse2 is known from 2001's pentium 4 cpus, and amd added such support in their athlon64 cpus...

« First ‹ Previous 1 .. 128 129 130 131 132 133 134 135 136 137 138 .. 152 Next › Last »