Source: chromium Version: 146.0.7680.71-1 Tags: upstream, patch, ftbfs, fixed-upstream Forwarded: https://boringssl-review.googlesource.com/c/boringssl/+/89508
Dear maintainer, Chromium FTBFS since 146.0.7680.71-1 on loong64 with the following log: > FAILED: [code=1] obj/third_party/boringssl/boringssl/urandom.o > clang++-19 <...> ../../third_party/boringssl/src/crypto/rand/urandom.cc -o > obj/third_party/boringssl/boringssl/urandom.o > ../../third_party/boringssl/src/crypto/rand/urandom.cc:72:8: error: unknown > type name 'CRYPTO_once_t'; did you mean 'bssl::CRYPTO_once_t'? > 72 | static CRYPTO_once_t rand_once = CRYPTO_ONCE_INIT; > | ^~~~~~~~~~~~~ > | bssl::CRYPTO_once_t > ../../third_party/boringssl/src/crypto/rand/../internal.h:530:24: note: > 'bssl::CRYPTO_once_t' declared here > 530 | typedef pthread_once_t CRYPTO_once_t; > | ^ > 1 error generated. I believe it is because USE_NR_getrandom is not defined on loong64 and thus the using namespace statement does not come into effect. Upstream has fixed this in [1]. I have tested with this patch and the build succeeded. I suggest that this patch can be applied to solve this problem. Cheers, Miao Wang [1]: https://boringssl-review.googlesource.com/c/boringssl/+/89508
