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

nullie commented on 2017-09-06 07:33 (UTC)

I've got an error trying to build 62.0.3192.0-1. Does it look like my local issue? The problem seems that wrong python is used, it's common for many builds that they expect python to be python2, not python3. [30959/32706] ../../native_client/toolchain/linux_x86/pnacl_newlib/bin/pnacl-clang -MMD -MF newlib_pnacl_nonsfi/obj/base/third_party/libevent/libevent/evutil.o.d -DNACL_TC_REV=efa3f5d8ef135ed2463a75ac4630d1c448021400 -DHAVE_CONFIG_H -DV8_DEPRECATION_WARNINGS -DUSE_OPENSSL_CERTS=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -I../../base/third_party/libevent/nacl_nonsfi -I../../native_client/src/public/linux_syscalls -I../.. -Inewlib_pnacl_nonsfi/gen -fno-strict-aliasing -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -fcolor-diagnostics --pnacl-allow-translate -arch x86-32-nonsfi --pnacl-bias=x86-32-nonsfi --target=i686-unknown-nacl -O2 -fno-ident -fdata-sections -ffunction-sections -fomit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-covered-switch-default -Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override -std=gnu11 -c ../../base/third_party/libevent/evutil.c -o newlib_pnacl_nonsfi/obj/base/third_party/libevent/libevent/evutil.o FAILED: newlib_pnacl_nonsfi/obj/base/third_party/libevent/libevent/evutil.o ../../native_client/toolchain/linux_x86/pnacl_newlib/bin/pnacl-clang -MMD -MF newlib_pnacl_nonsfi/obj/base/third_party/libevent/libevent/evutil.o.d -DNACL_TC_REV=efa3f5d8ef135ed2463a75ac4630d1c448021400 -DHAVE_CONFIG_H -DV8_DEPRECATION_WARNINGS -DUSE_OPENSSL_CERTS=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -I../../base/third_party/libevent/nacl_nonsfi -I../../native_client/src/public/linux_syscalls -I../.. -Inewlib_pnacl_nonsfi/gen -fno-strict-aliasing -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -fcolor-diagnostics --pnacl-allow-translate -arch x86-32-nonsfi --pnacl-bias=x86-32-nonsfi --target=i686-unknown-nacl -O2 -fno-ident -fdata-sections -ffunction-sections -fomit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-covered-switch-default -Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override -std=gnu11 -c ../../base/third_party/libevent/evutil.c -o newlib_pnacl_nonsfi/obj/base/third_party/libevent/libevent/evutil.o File "../../native_client/toolchain/linux_x86/pnacl_newlib/bin/pydir/loader.py", line 12 The environment variable PNACLPYTHON can override the python found in PATH''' ^ SyntaxError: Missing parentheses in call to 'print'

sl1pkn07 commented on 2017-08-15 12:27 (UTC)

is for making a selector for active the vaapi patch if detect the intel and AMD (and if nouveau is supported) drivers

xsmile commented on 2017-08-15 12:21 (UTC)

Don't know about nouveau.

sl1pkn07 commented on 2017-08-15 12:03 (UTC)

also with nouveau?

xsmile commented on 2017-08-15 11:56 (UTC) (edited on 2017-08-15 12:00 (UTC) by xsmile)

It would have been too good to be true if it worked without issues. I'm not up-to-date about the current status of vaapi_patch_r2.patch but the official commit definitely works with Intel and apparently helped an AMD user use VA-API while it didn't work with vaapi_patch_r2.patch. Now we know it causes issues with NVIDIA. EDIT: It would be great to collect reports and forward them to Daniel Charles (Google) while the official patchset is still being reviewed.

sl1pkn07 commented on 2017-08-15 10:13 (UTC)

with the vaapi patch https://sl1pkn07.wtf/paste/view/511741b3 :/

xsmile commented on 2017-08-14 18:06 (UTC) (edited on 2017-08-14 18:40 (UTC) by xsmile)

@sl1pkn07: Got it, I was missing the custom_toolchain flag. This way the compiler options are appended to the default ones set by GN and should override them, if necessary.

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

└───╼ cat /etc/makepkg.conf | grep -e CFLAGS -e CXXFLAGS CFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" CXXFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" DEBUG_CFLAGS="-g -fvar-tracking-assignments" DEBUG_CXXFLAGS="-g -fvar-tracking-assignments" [106/32501] /usr/bin/clang++ -Qunused-arguments -MMD -MF obj/base/base/profiler.o.d -DUSE_SYMBOLIZE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DCR_CLANG_REVISION=\"308728-3\" -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IMPLEMENTATION -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -funwind-tables -fPIC -pipe -pthread -fcolor-diagnostics -m64 -march=x86-64 -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-covered-switch-default -Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override -Wno-undefined-var-template -Wno-nonportable-include-path -Wno-address-of-packed-member -Wno-unused-lambda-capture -Wno-user-defined-warnings -fomit-frame-pointer -g0 -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wno-char-subscripts -Wexit-time-destructors -Wexit-time-destructors -O2 -fno-ident -fdata-sections -ffunction-sections -std=gnu++14 -fno-rtti -fno-exceptions -fvisibility-inlines-hidden -D_FORTIFY_SOURCE=2 -march=native -O2 -pipe -fstack-protector-strong -Wno-unknown-warning-option -c ../../base/debug/profiler.cc -o obj/base/base/profiler.o try with this (ugly) patch (for the PKGBUILD) https://sl1pkn07.wtf/paste/view/51cf7227 good luck!

xsmile commented on 2017-08-14 16:23 (UTC)

@sl1pkn07: The flags are used during GN compilation but not in the next compilation stage. For instance -march=native defaults to -march=x86-64, regardless of the settings in /etc/makepkg.conf. Thanks for testing btw.