On Tuesday, October 20, 2020 at 9:52:17 AM UTC+2 hugo.c...@essensium.com wrote:
> > > Hi Gerrit, > > If I understand correctly, I believe you try to cross-compile Go > applications to the PowerPC e500 architecture and as a first step you are > porting Go to this architecture. > > We recently ported Go applications such as Docker and its tools to > architectures not supported by upstream Go, but with an approach quite > different from yours (if I understood well). > > The procedure we follow, is: > > 1. Build the gccgo cross-toolchain with Buildroot: Buildroot currently > builds a toolchain by first building a gcc-initial, then proceeding to > build a gcc-final. We had to insert a new gcc compilation stage before > gcc-final can build the gccgo cross-compiler. This additional gcc > compilation stage makes go-tools available in the native environment that > are required for building the gccgo cross-compiler tools when gcc-final is > built. If I understand well this may be an important part of the solution > to your problem. > > 2. Patch the Buildroot environment to invoke gccgo as the compiler, rather > than gc, for compiling Go applications. We are planning to upstream this > and the previous step to Buildroot in the coming months. > Are these Buildroot changes available in a public repo? I have some interest in this, and was planning on doing something very similar in Buildroot, but if someone has already done, I would rather base any work on top of that. Best Regards, Mirza -- 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/40449fcb-2545-42d9-8ae2-20bdee5eb02fn%40googlegroups.com.
