Re: [Buildroot] [RFC] package/go: switch to gcc go instead of go-bootstrap

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

Hello,

On Thu, 26 May 2022 02:17:19 +0000
Joel Stanley <joel@jms.id.au> wrote:

> > The problem I see with this is that many external toolchains do not
> > provide Go support. While this will probably evolve over time, this is
> > not something that we can reasonably require right now.  
> 
> I use arm64 and ppc64le hosts for my buildrooting as they are the
> fastest machines I have access to. Neither are supported by
> go-bootstrap, so moving to gcc-go looks like a win for me.

Indeed.

> Likewise, we don't have prebuilt toolchains for those host CPUs so the
> question of external toolchains is not a factor.
> 
> I appreciate that my situation is unusual.

As Yann Morin suggested in another e-mail, maybe we need to support
both situations:

 * Building Go in 3 stages when using an external toolchain that
   doesn't have Go support. This would mean building Go 1.4 with the C
   compiler, then building Go 1.16 with Go 1.4, and finally building Go
   latest with Go 1.16.

 * Building Go in 2 stages with gcc-go when using an internal toolchain
   (in which we can enable Go support) or an external toolchain that
   has Go support.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot