On Tue, May 21, 2019 at 11:14 PM <taowangc...@gmail.com> wrote: > > Not sure someone reported this issue. > > Recently I had my golang compiler upgraded from 1.10.3 to 1.12.5. > A binary tool was built by 1.10 reported following errors when I executed it. > Obviously it's trying to include both x86 & AIX arch code, which is wrong. > I've checked my build environment, everything looks good. It's solved after I > "go get" for a new binary. > > Checked golang release note, looks like AIX is newly supported in 1.12, which > is not an understandable platform from 1.10 compiler. But how could the > binary trying to link both arch code ? Is it a known issue ?
The problem is that in the Go 1.12 sources "wasm" and "aix" are newly recognized build tags. Your program compiled with 1.10 does not understand that. So your 1.10 programs thinks that files like cpu_wasm.go and syscall_aix.go should be recognized, but when using 1.12 they are excluded due to build tags. You can work around this by adding build contraints like // +build wasm to all wasm files and // +build aix to all aix files. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcUAomNjQK-Z_u0OW9ESrUoh5JZYzXqj%3D79nRcbO1%2BY_CA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
