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
