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.020088
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 .. 18 19 20 21 22 23 24 25 26 27 28 .. 152 Next › Last »

sl1pkn07 commented on 2017-08-14 16:08 (UTC) (edited on 2017-08-14 16:08 (UTC) by sl1pkn07)

please use another downloadeable pastebin, for example https://sl1pkn07.wtf/paste

xsmile commented on 2017-08-14 15:48 (UTC)

@sl1pkn07: Use this patch for VA-API: https://0bin.net/paste/hIETCNLbL3hbqxln#MLskYbo-lMWhren2mQa5fo6Q0hI4Aakz9SlJUSsJ5Pf System Clang is used, this is not the issue. 64-bit and I already tried it. Environment variables are ignored, including CFLAGS, CXXFLAGS, CC and CXX.

sl1pkn07 commented on 2017-08-14 14:30 (UTC) (edited on 2017-08-14 14:31 (UTC) by sl1pkn07)

- for missing -i in L#463 and L#464, yes, do'h - for vaapi patch,this patchset can't apply in this version, maybe in the next release - about clang, 32 or 64 bits? is is 64bits, try edit the L#483 and set the system clang path. but i can't make sure it works

xsmile commented on 2017-08-14 13:31 (UTC)

@sl1pkn07: The two GCC patches are missing a "-i" before the file path and pause makepkg when disabling Clang. To enable VA-API with the current dev build, use the latest patchset from https://chromium-review.googlesource.com/c/532294 instead of vaapi_patch_r2.patch, it should apply without conflicts. Additionally 'use_vaapi=true' needs to be added to the flags (already present). See the comment section of https://aur.archlinux.org/packages/chromium-vaapi/ for success reports. Another issue - I tried building with 'clang_base_path="/usr"' to use system clang, but environment variables like CFLAGS are ignored. Is there any way to modify the variables while building with system clang without patching the source?

sl1pkn07 commented on 2017-08-13 07:32 (UTC)

never, i think

nicman23 commented on 2017-08-12 16:12 (UTC)

isn't vaapi in master?

sl1pkn07 commented on 2017-08-05 15:46 (UTC)

vaapi patch needs update https://chromium-review.googlesource.com/c/569529

trialuser commented on 2017-08-05 03:30 (UTC)

vaapi patch fails patching file build/config/compiler/BUILD.gn Hunk #1 succeeded at 1217 (offset 4 lines). patching file tools/gn/bootstrap/bootstrap.py patching file content/browser/accessibility/browser_accessibility_auralinux.cc patching file chrome/browser/about_flags.cc Hunk #1 succeeded at 1479 (offset 435 lines). patching file content/common/BUILD.gn Hunk #1 succeeded at 26 with fuzz 1 (offset 13 lines). Hunk #2 succeeded at 585 with fuzz 1 (offset 17 lines). patching file content/common/sandbox_linux/bpf_gpu_policy_linux.cc Hunk #1 succeeded at 25 with fuzz 1. Hunk #2 succeeded at 42 with fuzz 2. Hunk #5 succeeded at 322 (offset -7 lines). Hunk #6 succeeded at 365 (offset -7 lines). patching file content/common/va_wayland.sigs patching file content/gpu/BUILD.gn Hunk #1 succeeded at 103 (offset 11 lines). patching file content/gpu/gpu_main.cc Hunk #1 succeeded at 84 (offset -1 lines). Hunk #2 succeeded at 135 (offset -6 lines). patching file content/public/common/content_switches.cc Hunk #1 succeeded at 997 (offset -3 lines). patching file content/public/common/content_switches.h Hunk #1 succeeded at 283 (offset -8 lines). patching file gpu/config/software_rendering_list.json Hunk #1 succeeded at 371 (offset -24 lines). patching file media/BUILD.gn Hunk #1 FAILED at 396. Hunk #2 succeeded at 318 with fuzz 1 (offset -349 lines). 1 out of 2 hunks FAILED -- saving rejects to file media/BUILD.gn.rej patching file media/gpu/BUILD.gn Hunk #2 FAILED at 212. Hunk #3 FAILED at 221. Hunk #4 succeeded at 285 (offset 26 lines). 2 out of 4 hunks FAILED -- saving rejects to file media/gpu/BUILD.gn.rej patching file media/gpu/gpu_video_decode_accelerator_factory.cc Hunk #2 succeeded at 87 (offset 1 line). Hunk #3 succeeded at 140 (offset 1 line). Hunk #4 succeeded at 221 (offset -1 lines). patching file media/gpu/gpu_video_decode_accelerator_factory.h Hunk #1 succeeded at 105 (offset 4 lines). patching file media/gpu/ipc/service/BUILD.gn Hunk #1 succeeded at 50 (offset 3 lines). patching file media/gpu/ipc/service/gpu_video_decode_accelerator.cc Hunk #2 succeeded at 175 (offset 3 lines). patching file media/gpu/va_stub_header.fragment patching file media/gpu/vaapi_video_decode_accelerator.cc Hunk #1 succeeded at 364 (offset 6 lines). Hunk #2 succeeded at 384 (offset 6 lines). Hunk #3 succeeded at 400 (offset 6 lines). patching file media/gpu/vaapi_wrapper.cc Hunk #1 succeeded at 190 (offset 2 lines). Hunk #2 succeeded at 342 (offset 2 lines). Hunk #3 succeeded at 411 (offset 2 lines). Hunk #4 succeeded at 435 (offset 2 lines).

misc commented on 2017-06-16 22:46 (UTC)

You can switch to system freetype next build. Reason for the corruption I saw is this freetype commit… https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=ab2599ea3f09ba8da4f50b877021d23241d22609 … which will only be included in the next freetype version, by which time Skia should have been updated. Saves some 4 MiB.