1. Forum
  2. USENET
  3. muc.lists.freebsd.ports

  • aarch64 builds of chromium-144.0.7559.59 and later are failing for a compilation error

    From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.ports on Wed Feb 11 10:01:36 2026
    From Newsgroup: muc.lists.freebsd.ports

    [Note: variations of chromium are blacklisted for aarch64 on various
    official builder machines. They may be broken too but have no logs
    showing such.]


    The errors look like:

    ../../third_party/libaom/source/libaom/av1/encoder/hash.c -o obj/ third_party/libaom/libaom/hash.o

    ../../third_party/libaom/source/libaom/av1/encoder/hash.c:49:10: error: conflicting types for 'av1_get_crc32c_value_c'

    49 | uint32_t av1_get_crc32c_value_c(void *c, const uint8_t *buf,
    size_t len) {

    | ^

    ../../third_party/libaom/source/config/linux/arm64-cpu-detect/config/av1_rtcd.h:286:10:
    note: previous declaration is here

    286 | uint32_t av1_get_crc32c_value_c(void *crc_calculator, uint8_t
    *p, size_t length);

    | ^

    1 error generated.


    For *arm64-default these started as of:

    150arm64-default: chromium-144.0.7559.59
    build started at Thu Jan 22 02:27:00 UTC 2026

    143arm64-default chromium-144.0.7559.59
    build started at Fri Jan 23 20:45:25 UTC 2026

    Looks like 8 *arm64-default failures so far.


    For *arm64-quarterly they started as of:

    150arm64-quarterly: chromium-144.0.7559.109
    build started at Tue Feb 3 18:32:42 UTC 2026

    143arm64-quarterly: chromium-144.0.7559.109
    build started at Fri Feb 6 23:16:19 UTC 2026

    Looks like 3 *arm64-quarterly failures so far.
    --
    ===
    Mark Millard
    marklmi at yahoo.com



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Robert Nagy@rnagy@freebsd.org to muc.lists.freebsd.ports on Thu Feb 12 09:48:41 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi

    The latest update also fixes this issue on aarch64.

    On 11/02/26 10:01 -0800, Mark Millard wrote:
    [Note: variations of chromium are blacklisted for aarch64 on various
    official builder machines. They may be broken too but have no logs
    showing such.]


    The errors look like:

    ../../third_party/libaom/source/libaom/av1/encoder/hash.c -o obj/ third_party/libaom/libaom/hash.o

    ../../third_party/libaom/source/libaom/av1/encoder/hash.c:49:10: error: conflicting types for 'av1_get_crc32c_value_c'

    49 | uint32_t av1_get_crc32c_value_c(void *c, const uint8_t *buf,
    size_t len) {

    | ^

    ../../third_party/libaom/source/config/linux/arm64-cpu-detect/config/av1_rtcd.h:286:10:
    note: previous declaration is here

    286 | uint32_t av1_get_crc32c_value_c(void *crc_calculator, uint8_t
    *p, size_t length);

    | ^

    1 error generated.


    For *arm64-default these started as of:

    150arm64-default: chromium-144.0.7559.59
    build started at Thu Jan 22 02:27:00 UTC 2026

    143arm64-default chromium-144.0.7559.59
    build started at Fri Jan 23 20:45:25 UTC 2026

    Looks like 8 *arm64-default failures so far.


    For *arm64-quarterly they started as of:

    150arm64-quarterly: chromium-144.0.7559.109
    build started at Tue Feb 3 18:32:42 UTC 2026

    143arm64-quarterly: chromium-144.0.7559.109
    build started at Fri Feb 6 23:16:19 UTC 2026

    Looks like 3 *arm64-quarterly failures so far.


    --
    ===
    Mark Millard
    marklmi at yahoo.com


    --
    Regards,
    Robert Nagy


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.ports on Wed Feb 18 21:33:57 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Feb 12, 2026, at 00:48, Robert Nagy <rnagy@freebsd.org> wrote:
    The latest update also fixes this issue on aarch64.

    On 11/02/26 10:01 -0800, Mark Millard wrote:
    [Note: variations of chromium are blacklisted for aarch64 on various
    official builder machines. They may be broken too but have no logs
    showing such.]


    The errors look like:

    ../../third_party/libaom/source/libaom/av1/encoder/hash.c -o obj/
    third_party/libaom/libaom/hash.o

    ../../third_party/libaom/source/libaom/av1/encoder/hash.c:49:10: error:
    conflicting types for 'av1_get_crc32c_value_c'

    49 | uint32_t av1_get_crc32c_value_c(void *c, const uint8_t *buf,
    size_t len) {

    | ^

    ../../third_party/libaom/source/config/linux/arm64-cpu-detect/config/av1_rtcd.h:286:10:
    note: previous declaration is here

    286 | uint32_t av1_get_crc32c_value_c(void *crc_calculator, uint8_t
    *p, size_t length);

    | ^

    1 error generated.


    . . .
    For aarch64 chromium-145.0.7632.45 (main) is failing with:
    . . .
    FAILED: [code=1] obj/third_party/libaom/libaom/aarch64_cpudetect.o
    cc -MD -MF obj/third_party/libaom/libaom/aarch64_cpudetect.o.d -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -D_GNU_SOURCE -D__ARM_NEON__=1 -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_EXTENSIVE -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCPP_INSTRUMENTED_WITH_ASAN=0 -DCR_LIBCXX_REVISION=7ab65651aed6802d2599dcb7a73b1f82d5179d05 -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -I../../buildtools/third_party/libc++ -I../../third_party/libaom/source/config -I../../third_party/libaom/source/libaom -I../../third_party/libaom/source/config/linux/arm64-cpu-detect -fprofile-use=../../chrome/build/pgo_profiles/chrome-linux-7632-1770141097-089c305f4b85a18f72bff6608b243c61543787ec-c5f20e0fbaf89b7428e82eb8efc3ab21a9485d63.profdata -Wno-profile-instr-unprofiled -Wno-profile-instr-out-of-date -Wno-backend-plugin -mllvm -enable-ext-tsp-block-placement=1 -fno-delete-null-pointer-checks -fno-strict-overflow -fno-ident -fno-math-errno -fno-strict-aliasing -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -fcomplete-member-pointers -mbranch-protection=standard -mno-outline -ffile-compilation-dir=. -no-canonical-prefixes -O2 -fdata-sections -ffunction-sections -fno-unique-section-names -fno-omit-frame-pointer -g0 -fsanitize=array-bounds -fsanitize-trap=array-bounds -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall -Wno-unused-variable -Wno-c++11-narrowing -Wno-unused-but-set-variable -Wno-missing-field-initializers -Wno-unused-parameter -Wno-psabi -Wloop-analysis -Wno-unneeded-internal-declaration -Wno-cast-function-type -Wno-thread-safety-reference-return -Wno-nontrivial-memcall -Wno-uninitialized-const-pointer -Wno-exit-time-destructors -std=c11 -c ../../third_party/libaom/source/libaom/aom_ports/aarch64_cpudetect.c -o obj/third_party/libaom/libaom/aarch64_cpudetect.o
    ../../third_party/libaom/source/libaom/aom_ports/aarch64_cpudetect.c:210:2: error: "Runtime CPU detection selected, but no CPU detection method " "available for your platform. Rerun cmake with -DCONFIG_RUNTIME_CPU_DETECT=0."
    210 | #error \
    | ^ ../../third_party/libaom/source/libaom/aom_ports/aarch64_cpudetect.c:218:13: error: call to undeclared function 'arm_get_cpu_caps'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    218 | flags = arm_get_cpu_caps() & arm_cpu_env_mask();
    | ^ ../../third_party/libaom/source/libaom/aom_ports/aarch64_cpudetect.c:218:13: note: did you mean 'aom_arm_cpu_caps'?
    ../../third_party/libaom/source/libaom/aom_ports/aarch64_cpudetect.c:215:5: note: 'aom_arm_cpu_caps' declared here
    215 | int aom_arm_cpu_caps(void) {
    | ^
    216 | int flags = 0;
    217 | if (!arm_cpu_env_flags(&flags)) {
    218 | flags = arm_get_cpu_caps() & arm_cpu_env_mask();
    | ~~~~~~~~~~~~~~~~
    | aom_arm_cpu_caps
    2 errors generated.
    . . .
    That is from: <https://pkg-status.freebsd.org/ampere5/data/143arm64-default/fb751ba0f5ab/logs/errors/chromium-145.0.7632.45.log>
    ===
    Mark Millard
    marklmi at yahoo.com
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21b-Linux NewsLink 1.2