On Wed, Aug 31, 2016 at 1:57 AM, Tianon Gravi wrote:
> On 30 August 2016 at 01:31, YunQiang Su wrote:
>> I guess it is a bug of gccgo for mips64el.
>
> Yes, as Ian mentions in the thread I linked, the bug is that gccgo
> uses "mipsn64" as the GOARCH for mips64el in contrast to upstream
> golang.
On 30 August 2016 at 01:31, YunQiang Su wrote:
> I guess it is a bug of gccgo for mips64el.
Yes, as Ian mentions in the thread I linked, the bug is that gccgo
uses "mipsn64" as the GOARCH for mips64el in contrast to upstream
golang.
Do you have a good link that explains how I can test the
bootst
On Tue, Aug 30, 2016 at 2:37 PM, Mathieu Malaterre wrote:
> On Tue, Aug 30, 2016 at 8:31 AM, Mathieu Malaterre wrote:
>> On Sun, Aug 28, 2016 at 5:12 PM, Tianon Gravi wrote:
>>> Given that upstream officially supports bootstrapping via gccgo, I'd
>>> rather keep the discussion of "fix cross buil
On Tue, Aug 30, 2016 at 8:31 AM, Mathieu Malaterre wrote:
> On Sun, Aug 28, 2016 at 5:12 PM, Tianon Gravi wrote:
>> Given that upstream officially supports bootstrapping via gccgo, I'd
>> rather keep the discussion of "fix cross build" to a separate issue if
>> we can. I am interested in updatin
On Sun, Aug 28, 2016 at 5:12 PM, Tianon Gravi wrote:
> Given that upstream officially supports bootstrapping via gccgo, I'd
> rather keep the discussion of "fix cross build" to a separate issue if
> we can. I am interested in updating the packaging to properly support
> cross-building, but consid
Given that upstream officially supports bootstrapping via gccgo, I'd
rather keep the discussion of "fix cross build" to a separate issue if
we can. I am interested in updating the packaging to properly support
cross-building, but consider it a secondary concern to adding more
architectures.
That
6 matches
Mail list logo
