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.005026
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 .. 48 49 50 51 52 53 54 55 56 57 58 .. 152 Next › Last »

jebarb commented on 2015-03-15 19:57 (UTC)

@sl1pkn07 Looks like I was somehow running out of memory, causing segfaults. Nothing useful in any logs. Computer was becoming 99% unresponsive. Strange, because it was failing on a system with 12G memory with 6G tmpfs. Bumped it up to 8G and added a swapfile, now the build is moving along fine.

sl1pkn07 commented on 2015-03-14 08:13 (UTC)

@jbarb For first error. Please paste more log (search 'FAILED' string). For second error, i'll investigare. One cuestión. You use 32 or 64 bits? Greetings

jebarb commented on 2015-03-13 23:55 (UTC)

Package is failing to build with packaged clang, system clang, and gcc on two devices. Error with packaged clang: [1837/2229] Building CXX object tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o FAILED: /usr/bin/c++ -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wno-comment -std=c++11 -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -fno-strict-aliasing -O3 -Itools/clang/lib/ASTMatchers/Dynamic -I/tmp/pacaurtmp-jebarb/chromium-dev/src/chromium-42.0.2311.22/third_party/llvm/tools/clang/lib/ASTMatchers/Dynamic -I/tmp/pacaurtmp-jebarb/chromium-dev/src/chromium-42.0.2311.22/third_party/llvm/tools/clang/include -Itools/clang/include -Iinclude -I/tmp/pacaurtmp-jebarb/chromium-dev/src/chromium-42.0.2311.22/third_party/llvm/include -UNDEBUG -fno-exceptions -fno-rtti -MMD -MT tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o -MF tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o.d -o tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o -c /tmp/pacaurtmp-jebarb/chromium-dev/src/chromium-42.0.2311.22/third_party/llvm/tools/clang/lib/ASTMatchers/Dynamic/Registry.cpp c++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <https://bugs.archlinux.org/> for instructions. [1837/2229] Building CXX object tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaDeclCXX.cpp.o ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Error with system clang (gcc error is similar): -> Starting building Chromium... File "build/gyp_chromium", line 118 except SyntaxError, e: ^ SyntaxError: invalid syntax ==> ERROR: A failure occurred in build().

ethail commented on 2015-03-09 22:54 (UTC)

Would it be too much trouble to add some kind of config option that results on using ccache when the system clang is enabled? It would have to change lines 364 onwards for something like this: msg2 "Setup system clang" export CC="ccache clang -Qunused-arguments" export CXX="ccache clang++ -Qunused-arguments" export CCACHE_CPP2=yes export CCACHE_SLOPPINESS=time_macros export CXXFLAGS="${CXXFLAGS} -Wno-unknown-warning-option" For those that have set-up ccache, the change could result in a speed-up of subsequent rebuilds or updates. I know anyone could make that changes manually every time or something like that, but having it as a config option in the PKGBUILD seemed a better way to handle it. Thanks in advance

sl1pkn07 commented on 2015-02-27 10:38 (UTC)

Ops! I whill fix when go to home Greerings

ledti commented on 2015-02-27 04:51 (UTC)

I noticed that the chromium-dev wrapper looks for /etc/chromium/default rather than /etc/chromium-dev/default, which makes chromium-dev incompatible with all the pepper-flash packages unless you also have chromium installed (or you edit the wrapper). Is that intentional?

sl1pkn07 commented on 2015-02-25 05:42 (UTC)

ouch!

« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 152 Next › Last »