Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation failed from building source #234

Open
njovy opened this issue Aug 16, 2024 · 1 comment
Open

Installation failed from building source #234

njovy opened this issue Aug 16, 2024 · 1 comment

Comments

@njovy
Copy link

njovy commented Aug 16, 2024

FAILED: crypto_test_data.cc 
cd /root/dist/curl-impersonate/build/boringssl && /usr/bin/go run util/embed_test_data.go -file-list /root/dist/curl-impersonate/build/boringssl/build/embed_test_data_args.txt > /root/dist/curl-impersonate/build/boringssl/build/crypto_test_data.cc
# command-line-arguments
util/embed_test_data.go:81:16: undefined: os.ReadFile
util/embed_test_data.go:131:16: undefined: os.ReadFile
note: module requires Go 1.19
[3/762] Generating vpaes-armv8-win.S
ninja: build stopped: subcommand failed.
make: *** [Makefile:271: /root/dist/curl-impersonate/build/boringssl/build/lib/libssl.a] Error 1

I tried to install with building from source on Ubuntu 20.04.2 but can't run make chrome-build.
Any help would be highly appreciated. Thank you in advance.

@beddiecrokka
Copy link

Having os.ReadFile be undefined, generally means your Go version is old and needs to be updated. os.ReadFile was introduced in Go 1.16 (from Feb 2021) and as you can see, the note saying module requires Go 1.19 means that's going to be the minimum version of Go you need to be able to build that portion. I'm not sure what the minimum version of Go is required for chrome-build though.

Note, I had the same problem (my Go was v1.4) and I had upgraded Go via source multiple times to get to the latest v1.23.1 and the thing is, after updating, make chrome-build was still using the older Go. Turns out 'gmake chrome-clean' wasn't enough to clear out the cached version of Go that was initially found so 'gmake chrome-build' kept trying to force the use of the older Go for me. I had to do a 'gmake clean' in order for the cached versions to be done away with and then redo ../configure in order to get it to use the newest Go I built. Hope that helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants