This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
libgo multilib issues.
- From: David Daney <ddaney at caviumnetworks dot com>
- To: Ian Lance Taylor <iant at google dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Thu, 27 Jan 2011 10:34:54 -0800
- Subject: libgo multilib issues.
Ian,
In trying to build libgo on mips64-linux we try to build all three
multilibs (o32, n32 and n64 ABIs)
For the n32 ABI, the configure script generates syscall_arch.go:
-----------
package syscall
const ARCH = "mips64"
const OS = "linux"
-----------
The Makefile has GOARCH = mips64, so it is trying to compile my new
syscalls/syscall_linux_mips64.go.
So far so good.
But now what will happen for the n64 ABI? It has the exact same GOARCH.
This is not good because n64 will need a different
syscalls/syscall_linux_${GOARCH}.go
Actually I think my syscall_linux_mips.go can be shared between both the
o32 and n32 libraries.
How to sort this out?
David Daney