cmd/go: go build fails with linker error when using clang v4.0.1

[OneOfOne]

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

➤ git describe --tags
go1.9beta2-129-g504deee608

What operating system and processor architecture are you using (go env)?

Arch Linux 64bit

What did you do?

$ env GOROOT_BOOTSTRAP=/usr/src/go1.4 CC=clang GOGC=off bash make.bash

Note that using CC=gcc works fine.

What did you expect to see?

Successful compile of the go toolset

What did you see instead?

............
cmd/vet
# runtime/cgo
/usr/bin/ld: -r and -pie may not be used together
clang-4.0: error: linker command failed with exit code 1 (use -v to see invocation)
cmd/go/internal/envcmd
............

[ALTree]

The equivalent GCC issue was #20276. It looks like the fix (CL 18359), which was also backported to go1.4-bootstrap (CL 42910), does not cover and/or fails with clang.

[ALTree]

cc @ianlancetaylor

[ALTree]

@OneOfOne I assume you are using the latest go1.4 bootstrap archive, i.e. go1.4-bootstrap-20170531.tar.gz.

[OneOfOne]

@ALTree I'm using the release-branch.go1.4 branch, trying to recompile it however absolutely fails, with both clang and gcc.

https://gist.github.com/OneOfOne/a9116d4c85c32141282fcf9a2973fbd2

edit:

Note that this is a separate issue, I still can't build go with clang even with go1.8 as bootstrap.

[ALTree]

Ok so the clang issue is the -r and -pie may not be used together issue, already fixed for GCC (see my comment above), and it's the topic of this issue.

Can you file another issue for the other problem? The fact that compiling go1.4 bootstrap fails with

# net
cannot load DWARF output from $WORK/net/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0
# os/user
cannot load DWARF output from $WORK/os/user/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0

on your system, even with GCC. Please include system info and the gcc version in the report.

[ALTree]

I still can't build go with clang even with go1.8 as bootstrap.

Wait, does this also affect go1.8? i.e. you can't build go1.8 from source with clang?

EDIT: ah yes I get it now. Sorry for the misunderstanding.

[OneOfOne]

@ALTree I hadn't tried until you mentioned it, no I can't build 1.8 from source either.