-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
error: incompatible types in assignment when building with Docker/go #367
Comments
There is a similar issue: moby/moby#16701 |
netlink has been refactored, but I think the uint8 and int8 usage is not changed. So it should be existed on the latest code. |
I managed to get around this error by using go 1.4.2 rather than gcc-go 1.4.2... binaries available for ARM - http://dave.cheney.net/unofficial-arm-tarballs The issues appears to be with gcc-go then. Alex |
@hqhq is right, this was a point in time failure, fixed in the latest code. GCCGO issue. |
Great, since the latest gccgo has fixed it, and @alexellis already workarounded it, I think we can close this issue. |
Thanks everyone. |
Can you give us more info on the fix in both docker and gcc-go? I am having this same issue when packaging docker with gcc-go ... thanks |
is this one ? |
Hi, Here is the original golang issue on this problem golang/go#11469. As a result a fix was needed in gccgo and in Docker. Unfortunately the gccgo fix did not make it into gcc 5.2 but shortly after. The fix went into gcc trunk as well. Building gccgo from a current snapshot in the gcc 5 branch or from gcc trunk will have the correct gccgo fix. It will be in the next release from the gcc 5 branch after 5.2 (5.2.1 or 5.3 not sure which) and the gcc 6 release. Sorry for the inconvenience. |
While building docker tagged branch v1.8.1 on following configuration:
uname -a
Linux 4.1.10-2-ARCH #1 SMP PREEMPT Sat Oct 10 08:33:21 MDT 2015 armv7l GNU/Linux
$ go version
go version go1.4.2 gccgo (GCC) 5.2.0 linux/arm
During the build I get this error:
Please could you advise?
The text was updated successfully, but these errors were encountered: