You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building gollvm with Github Actions: "grep: gen-sysinfo.go: No such file or directory" and "error: At most two relocations per offset are supported"
#42651
Does this issue reproduce with the latest release?
Indeed
What operating system and processor architecture are you using (go env)?
Ubuntu 18.04.5 LTS, adopted for Azure's instances
What did you do?
I was trying to use Github Actions to automate gollvm's release process. My run
What did you expect to see?
Successful compilation of libgo and all required sub-targets.
What did you see instead?
Well, I see that llvm-goc is built.
I see that the back-end test suite ran successfully.
But some auto-generation not working normally, for gen-sysinfo.go.
Consider checking archived logs here and a single file/raw listing here .
I see the first occurrence of reported file absence at
2020-11-15T23:36:42.1083177Z [1537/2664] Creating /home/runner/work/clang_test_cpu_features/clang_test_cpu_features/clang_test_cpu_features/build_release/tools/gollvm/libgo/tmp-os_user_linknames.go
2020-11-15T23:36:42.1089654Z grep: gen-sysinfo.go: No such file or directory
. It is repeating dozens of times.
2020-11-15T23:36:42.8153253Z [1560/2664] Generating /home/runner/work/clang_test_cpu_features/clang_test_cpu_features/clang_test_cpu_features/build_release/tools/gollvm/libgo/gen-sysinfo.go
2020-11-15T23:36:42.8164171Z error: At most two relocations per offset are supported
Probably a verbose logging should be enabled, to track this.
Btw is it depending on Clang's version?
What version of Go are you using (
go version
)?gollvm aka Go 1.15.5
Does this issue reproduce with the latest release?
Indeed
What operating system and processor architecture are you using (
go env
)?Ubuntu 18.04.5 LTS, adopted for Azure's instances
What did you do?
I was trying to use Github Actions to automate gollvm's release process.
My run
What did you expect to see?
Successful compilation of libgo and all required sub-targets.
What did you see instead?
Well, I see that llvm-goc is built.
I see that the back-end test suite ran successfully.
But some auto-generation not working normally, for gen-sysinfo.go.
Consider checking archived logs here and a single file/raw listing here .
I see the first occurrence of reported file absence at
Probably a verbose logging should be enabled, to track this.
Btw is it depending on Clang's version?
I think it is triggered here .
CC @thanm @cherrymui @ianlancetaylor
The text was updated successfully, but these errors were encountered: