Re: [go-nuts] gccgo problem compiling go from source

2020-11-10 Thread 'Mirza Krak' via golang-nuts
On Tue, Nov 10, 2020 at 10:06 AM Hugo Cornelis wrote: > > Hi Mirza, > > On Thu, Nov 5, 2020 at 3:18 PM 'Mirza Krak' via golang-nuts > wrote: >> >> On Tuesday, October 20, 2020 at 9:52:17 AM UTC+2 hugo.c...@essensium.com >> wrote: >>> >>> 1. Build the gccgo cross-toolchain with Buildroot:

Re: [go-nuts] gccgo problem compiling go from source

2020-11-10 Thread Hugo Cornelis
applications. We are planning to >>>>> upstream >>>>> this and the previous step to Buildroot in the coming months. >>>>> >>>>> 3. Implement Go system call bindings: The sys package of the Go >>>>> runtime implements system c

Re: [go-nuts] gccgo problem compiling go from source

2020-11-10 Thread Hugo Cornelis
Hi Mirza, On Thu, Nov 5, 2020 at 3:18 PM 'Mirza Krak' via golang-nuts < golang-nuts@googlegroups.com> wrote: > On Tuesday, October 20, 2020 at 9:52:17 AM UTC+2 hugo.c...@essensium.com > wrote: > >> 1. Build the gccgo cross-toolchain with Buildroot: Buildroot currently >> builds a toolchain by

Re: [go-nuts] gccgo problem compiling go from source

2020-11-09 Thread Gerrit Binnenmars
call bindings for your target >>>> environment (so the PowerPC e500 in your case). Most of our development >>>> time was spent in this last step (it is tricky). >>>> >>>> Using this procedure we have ported Docker and its dependencies an

Re: [go-nuts] gccgo problem compiling go from source

2020-11-05 Thread 'Mirza Krak' via golang-nuts
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

Re: [go-nuts] gccgo problem compiling go from source

2020-10-28 Thread Hugo Cornelis
ocker and its dependencies and >>> tools to several ppc 32 bit architectures. >>> >>> I hope this helps. >>> >>> Hugo >>> >>> >>> >>> On Tue, Oct 20, 2020 at 6:20 AM gerritbinnenmars >>> wrote: >>> >&

Re: [go-nuts] gccgo problem compiling go from source

2020-10-23 Thread Hugo Cornelis
ar. >>> What I am doing is the other way around: using gccgo to build the "go" >>> cmd. >>> So clone the "go" source from github and then go build -compiler gccgo >>> ./cmd/go >>> >>> Gerrit >>> >>> Oorspr

Re: [go-nuts] gccgo problem compiling go from source

2020-10-22 Thread Gerrit Binnenmars
ccgo >> ./cmd/go >> >> Gerrit >> >> Oorspronkelijk bericht >> Van: Ian Lance Taylor >> Datum: 20-10-20 04:25 (GMT+01:00) >> Aan: Gerrit Binnenmars >> Cc: golang-nuts >> Onderwerp: Re: [go-nuts] gccgo problem compi

Re: [go-nuts] gccgo problem compiling go from source

2020-10-22 Thread Gerrit Binnenmars
Ian, thanks for clearing that up. Will have another look at crosstool-ng. On Tue, Oct 20, 2020 at 9:21 PM Ian Lance Taylor wrote: > > On Tue, Oct 20, 2020 at 8:17 AM Gerrit Binnenmars > wrote: > > > > You are correct, what I try is to cross-compile a go application (in this > > case Mender

Re: [go-nuts] gccgo problem compiling go from source

2020-10-20 Thread Ian Lance Taylor
On Tue, Oct 20, 2020 at 8:17 AM Gerrit Binnenmars wrote: > > You are correct, what I try is to cross-compile a go application (in this > case Mender client) for the ppc platform (e500 on a MFC8555 processor). > 1. I used crosstool-ng instead of buildroot. It has support for "go" as >

Re: [go-nuts] gccgo problem compiling go from source

2020-10-20 Thread Gerrit Binnenmars
;> >> On Tue, Oct 20, 2020 at 6:20 AM gerritbinnenmars >> wrote: >> >>> Hello Ian, >>> Thanks for the quick reaction. It seems my request was not clear. >>> What I am doing is the other way around: using gccgo to build the "go" >&

Re: [go-nuts] gccgo problem compiling go from source

2020-10-20 Thread Gerrit Binnenmars
am doing is the other way around: using gccgo to build the "go" >> cmd. >> So clone the "go" source from github and then go build -compiler gccgo >> ./cmd/go >> >> Gerrit >> >> Oorspronkelijk bericht >> Van: Ian Lance Taylor >>

Re: [go-nuts] gccgo problem compiling go from source

2020-10-20 Thread David Riley
On Oct 20, 2020, at 2:38 AM, fge...@gmail.com wrote: > > After looking at the list of supported platforms on build.golang.org > and looking at the golang-nuts and golang-dev mailing list archives, I > can't see the ppc e500 as a supported hardware platform for the go > compiler (available on

Re: [go-nuts] gccgo problem compiling go from source

2020-10-20 Thread Hugo Cornelis
thub and then go build -compiler gccgo > ./cmd/go > > Gerrit > > Oorspronkelijk bericht > Van: Ian Lance Taylor > Datum: 20-10-20 04:25 (GMT+01:00) > Aan: Gerrit Binnenmars > Cc: golang-nuts > Onderwerp: Re: [go-nuts] gccgo problem compiling go fro

Re: [go-nuts] gccgo problem compiling go from source

2020-10-20 Thread fgergo
On 10/20/20, gerritbinnenmars wrote: > Hello Ian,Thanks for the quick reaction. It seems my request was not > clear.What I am doing is the other way around: using gccgo to build the "go" > cmd.So clone the "go" source from github and then go build -compiler gccgo > ./cmd/goGerrit Assuming you

Re: [go-nuts] gccgo problem compiling go from source

2020-10-19 Thread gerritbinnenmars
--Van: Ian Lance Taylor Datum: 20-10-20 04:25 (GMT+01:00) Aan: Gerrit Binnenmars Cc: golang-nuts Onderwerp: Re: [go-nuts] gccgo problem compiling go from source On Mon, Oct 19, 2020 at 2:06 PM Gerrit Binnenmars wrote:>> I used crosstool-ng successfully to build a go compiler for pp

Re: [go-nuts] gccgo problem compiling go from source

2020-10-19 Thread Ian Lance Taylor
On Mon, Oct 19, 2020 at 2:06 PM Gerrit Binnenmars wrote: > > I used crosstool-ng successfully to build a go compiler for ppc e500. > Unfortunately go build does not support ppc therefore go needs to be > build from source using the amd64 gccgo compiler that I also build > with crosstool-ng. > >