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
I am on 64-bit x86 Fedora Linux with kernel 5.19.4-200.fc36.x86_64. My TMP/TMPDIR is either an ext4 filesystem or a tmpfs filesystem, depending on the exact build setup, and the final install destination is on a ZFS filesystem.
I believe that this means that error checks on copy_file_range(2) aren't redundant because (apparently) not all filesystems support this.
What did you do?
Tried to build go with ./all.bash.
What did you expect to see?
A successful build.
What did you see instead?
Building Go cmd/dist using /data/code/go-lang/v1.19. (go1.19 linux/amd64)
Building Go toolchain1 using /data/code/go-lang/v1.19.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
go install internal/unsafeheader: copying /tmp/go-build1432901531/b007/_pkg_.a to /data/code/go-lang/go/pkg/linux_amd64/internal/unsafeheader.a: write /data/code/go-lang/go/pkg/linux_amd64/internal/unsafeheader.a: copy_file_range: invalid cross-device link
go install internal/goos: copying /tmp/go-build1432901531/b014/_pkg_.a to /data/code/go-lang/go/pkg/linux_amd64/internal/goos.a: write /data/code/go-lang/go/pkg/linux_amd64/internal/goos.a: copy_file_range: invalid cross-device link
go install internal/goarch: copying /tmp/go-build1432901531/b006/_pkg_.a to /data/code/go-lang/go/pkg/linux_amd64/internal/goarch.a: write /data/code/go-lang/go/pkg/linux_amd64/internal/goarch.a: copy_file_range: invalid cross-device link
go install internal/goexperiment: copying /tmp/go-build1432901531/b013/_pkg_.a to /data/code/go-lang/go/pkg/linux_amd64/internal/goexperiment.a: write /data/code/go-lang/go/pkg/linux_amd64/internal/goexperiment.a: copy_file_range: invalid cross-device link
[...]
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?The last working version is:
Does this issue reproduce with the latest release?
No.
What operating system and processor architecture are you using (
go env
)?go env
OutputI am on 64-bit x86 Fedora Linux with kernel 5.19.4-200.fc36.x86_64. My TMP/TMPDIR is either an ext4 filesystem or a tmpfs filesystem, depending on the exact build setup, and the final install destination is on a ZFS filesystem.
I believe that this means that error checks on
copy_file_range(2)
aren't redundant because (apparently) not all filesystems support this.What did you do?
Tried to build go with
./all.bash
.What did you expect to see?
A successful build.
What did you see instead?
The text was updated successfully, but these errors were encountered: