Skip to content
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

Closed
alexellis opened this issue Oct 26, 2015 · 9 comments
Closed

Comments

@alexellis
Copy link

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:

vendor/src/github.com/opencontainers/runc/libcontainer/netlink/netlink_linux.go: 1260:26: error: incompatible types in assignment (cannot use type uint8 as type int8)

ifr.IfruHwaddr.Data[i] = ifrDataByte(hw[i])

^

Please could you advise?

@hqhq
Copy link
Contributor

hqhq commented Oct 26, 2015

There is a similar issue: moby/moby#16701
I don't have a box to reproduce this, maybe ping @brahmaroutu since there is a similar issue on ppc64le with gccgo.

@hqhq
Copy link
Contributor

hqhq commented Oct 26, 2015

netlink has been refactored, but I think the uint8 and int8 usage is not changed. So it should be existed on the latest code.

@alexellis
Copy link
Author

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

@brahmaroutu
Copy link

@hqhq is right, this was a point in time failure, fixed in the latest code. GCCGO issue.

@hqhq
Copy link
Contributor

hqhq commented Oct 28, 2015

Great, since the latest gccgo has fixed it, and @alexellis already workarounded it, I think we can close this issue.

@alexellis
Copy link
Author

Thanks everyone.

@jordimassaguerpla
Copy link

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

@jordimassaguerpla
Copy link

is this one

gcc-mirror/gcc@e487326

?

@laboger
Copy link

laboger commented Oct 28, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants