-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
cmd/vendor/github.com/google/pprof/internal/binutils: TestObjFile failure #26584
Comments
/cc @ianlancetaylor |
CC @rauls5382 |
ld 2.22 is surprisingly old; it was released in 2011. I wonder if that could be causing this somehow. |
I think you may have build go over your bootstrap version.
…On 25 July 2018 at 14:37, Agniva De Sarker ***@***.***> wrote:
/cc @ianlancetaylor <https://github.com/ianlancetaylor>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#26584 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAcA2dSmZ8PgLnLyjcxTt8seaAupUBXks5uJ_YLgaJpZM4VfWKO>
.
|
also hitting this with ld 2.22, compiled from go-1.9. I can provide more info if it would be helpful. |
Note that go 1.9.4 seems to pass this test (same everything else)
... which is because the TestObjFile code was introduced later. Also note that #23888 seems related. |
When ld version is too old (Debian 7 comes with version 2.2 which is too old), golang testsuite fail with: binutils_test.go:237: SourceLine for main: expect [{main /tmp/hello.c 3}]; got [{main 0}] see also golang/go#26584
When ld version is too old (Debian 7 comes with version 2.2 which is too old), golang testsuite fail with: binutils_test.go:237: SourceLine for main: expect [{main /tmp/hello.c 3}]; got [{main 0}] see also golang/go#26584 We explicitly use gcc 8.2, but what we need is gcc > 5.5 because of golang/go#24046 When 8.2 (or newer) becomes the default SlapOS gcc, there should be no problem in dropping the explicit version and using ${gcc:location} here.
I think the right fix is to check the binutils version and skip the test for a sufficiently old version. But this change should be made in the upstream sources. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.10.3 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?bash-3.2$ ld --version
GNU ld (GNU Binutils) 2.22
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jhart/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/jhart/go"
GORACE=""
GOROOT="/home/jhart/temp/temp/go"
GOTMPDIR=""
GOTOOLDIR="/home/jhart/temp/temp/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build636359804=/tmp/go-build -gno-record-gcc-switches"
What did you do?
What did you expect to see?
All tests should have been passed successfully
What did you see instead?
The text was updated successfully, but these errors were encountered: