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
x/tools: tests fail with gccgo #17999
Comments
Skimming quickly, it looks like everything compiles but some tests fail, all due to the same bug, locating source code. |
Related to: #11811 for Go 1.8. |
The short answer is that nobody ever tried to make it work. As Brad said, most of the tests are failing because |
@alandonovan , I don't know the reasons for the In fact, if I run strace on one of the failing tests, I see that for reaching (for example)
So, no matter what the GOROOT is, it will still not work. |
@alandonovan |
@iant So how does the TestDeps test in the standard |
The |
@TheTincho The only way tools from I have been struggling to use gccgo to verify whether even this is sufficient, and in any case |
@alandonovan Thanks for looking into this. I understand this is not tested and adding the go sources just for this does not make sense. In any case, I would like to be able to provide the subset of x/tools that can work with gccgo, but I don't know which tests fail because the library can't work there, or just because the tests are requiring source code. Are you saying that all of it requires the sources for the stdlib? |
You should be able to use the following packages beneath |
What version of Go are you using (
go version
)?go version go1.6.1 gccgo (Debian 6.2.0-13) 6.2.0 20161109
What operating system and processor architecture are you using (
go env
)?Debian, all architectures not directly supported by the official compiler.
Hi, I am one of the people maintaining go libraries in Debian, and I have been trying to get x/tools to work with gccgo with no luck. We aim to provide golang support in all of our architectures, and so we use gccgo in mips*, alpha, powerpc, and now s390x.
We are able to build x/tools, but the tests fail spectacularly. I wonder if we are doing something very wrong, or is it that nobody ever tried to make it work there. Many errors seem to be related to tools expecting source code to be present for the stdlib, for example.
I would really appreciate if somebody could take a look at this, we are getting close to the freeze (before Debian stable is released), and I would like to fix that in time. The log from a sample build in mipsel is attached:
golang-golang-x-tools_0.0~git20161028.0.b814a3b+ds-3_mipsel.build.txt
The text was updated successfully, but these errors were encountered: