If you're impatient, I'm pretty sure recent enough docker builds with
gccgo on arm64.
On 14 October 2015 at 12:43, Potter, Tim (Converged Cloud)
wrote:
> Hi tianon. I was curious what your plans were for uploading Go 1.5 to
> unstable. Is there anything you can share?
On 16 October 2015 at 06:40, Michael Stapelberg wrote:
>
>
> On Thu, Oct 15, 2015 at 6:44 PM, Tianon Gravi wrote:
>>
>> On 13 October 2015 at 16:43, Potter, Tim (Converged Cloud)
>> wrote:
>> > Hi tianon. I was curious what
Sure! :) On the Docker end, the discussion is in
https://github.com/docker/docker/pull/15703 (and you're correct that
it's Docker doing something "wrong", but isn't it still worth checking
so we don't get random FTBFS? or do we just not worry about it and do
something about them as they come?)
On 15 October 2015 at 10:40, Michael Stapelberg wrote:
> FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to
> its Go 1 stability guarantee, and any package which breaks likely did
> something wrong in the first place :). If this is the only thing
On Thu, Oct 15, 2015 at 6:44 PM, Tianon Gravi wrote:
> On 13 October 2015 at 16:43, Potter, Tim (Converged Cloud)
> wrote:
> > Hi tianon. I was curious what your plans were for uploading Go 1.5 to
> unstable. Is there anything you can share?
>
> Go
Hi tianon. I was curious what your plans were for uploading Go 1.5 to
unstable. Is there anything you can share?
I’m pretty keen on seeing Docker running on arm64 which should get pulled in as
golang-go is a B-D.
Thanks,
Tim.
___