Igen -I././third_party/abseil-cpp -fno-delete-null-pointer-checks -fno-ident -fno-strict-aliasing -param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -fcrash-diagnostics-dir=././tools/clang/crashreports -mllvm -instcombine-lower-dbg-declare=0 -ffp-contract=off -flto=thin -fsplit-lto-unit -fwhole-program-vtables -mbranch-protection=standard -target=aarch64-linux-gnu -mno-outline -ffile-compilation-dir=. " CXX obj/third_party/abseil-cpp/absl/debugging/stacktrace/stacktrace.oįAILED: obj/third_party/abseil-cpp/absl/debugging/stacktrace/stacktrace.oĬlang++ -MMD -MF obj/third_party/abseil-cpp/absl/debugging/stacktrace/stacktrace.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -D_GNU_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DABSL_ALLOCATOR_NOTHROW=1 -I./. And trying the Arch ARM 116 vanilla chromium PKGBUILD from gives the same error at the bottom Ungoogled-chromium does not compile anymore past version 115 which got broken by an re2 update and 115 relies on re2 10, but the upgrade was to 11, with both the aur PKGBUILD from and this PKGBUILD, and I used to put the same patches Arch Linux ARM puts onto their chromium PKGBUILD, and that one also doesnt work, and the patches used to work until now, and removing the patches also has no effect.Īlso, on a fresh Arch ARM copy on another ARM device with all dependencies, it still fails to build.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |