nal),
>>>> the golang-sys/unix package is (can be) shipped in the folder
>>>> golang-sys/unix of the application you want to build (this is Docker and
>>>> tools in our case). The golang-sys package needs to be patched in each
>>>> application t
> 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 -compi
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
I referred to this link on the internet:
https://github.com/golang/go/wiki/GccgoCrossCompilation#build-a-cross-gccgo-aware-version-of-the-go-tool
On Tuesday, October 20, 2020 at 5:18:05 PM UTC+2 Gerrit Binnenmars wrote:
> Hello Hugo,
>
> You are correct, what I try is to cross-com
at 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
>>
>> Oorspronkelijk bericht ----
>> Van: Ian Lance Taylor
>
in internal/goroot/gccgo.go
I included the output of my build script below. Any help or tips are
welcome.
With kind regards,
Gerrit Binnenmars
Info:
This is crosstool-NG version 1.24.0.191_364ed7a
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/mai