Comment 1 for bug 1921110

Fun fact: originally I faced this issue when compiling BoringSSL. I had both CMake and Go installed from snap. BoringSSL can't be built with this setup, since CMake invokes "go run file.go > file.c" for code generation during build, and it produces an empty file instead of the desired code.

For people coming from Google: if you're using snap and get strange linker errors when building BoringSSL, you're probably facing the same issue:

/usr/bin/ld: libcrypto.a(err.c.o): in function `ERR_reason_error_string':
boringssl/crypto/err/err.c:579: undefined reference to `kOpenSSLReasonValuesLen'
/usr/bin/ld: boringssl/crypto/err/err.c:578: undefined reference to `kOpenSSLReasonValues'
/usr/bin/ld: boringssl/crypto/err/err.c:578: undefined reference to `kOpenSSLReasonStringData'