From: "Steven Stallion" <sstallion@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Building go1.12.14
Date: Wed, 1 Jan 2020 12:08:44 -0600 [thread overview]
Message-ID: <fba80a0426a6f7b9feb9a45f813fc68f@gunge.quuxotic.net> (raw)
In-Reply-To: <ea3a7963-c277-4a25-b251-7ccca277fa63@www.fastmail.com>
> I think the second issue has been fixed in Go 1.13.
>
> You can follow the issues their resolution on https://github.com/golang/go/labels/OS-Plan9.
Thanks. I'm beginning to suspect there may be some additional patches
needed that I may not have applied. I've noticed when attempting to
hget files from GitHub that I'm running into issues with TLS:
tlsClient: protocol version not supported
I've double checked, and libsec-x509-sha2.diff is indeed applied. Do
you know of any additional patches that are needed to update TLS
support?
Cheers,
Steve
next prev parent reply other threads:[~2020-01-01 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 16:20 Steven Stallion
2020-01-01 17:12 ` [9fans] " David du Colombier
2020-01-01 18:08 ` Steven Stallion [this message]
2020-01-01 19:04 ` David du Colombier
2020-01-01 19:10 ` David du Colombier
2020-01-01 21:36 ` Steven Stallion
2020-01-01 22:08 ` David du Colombier
2020-01-01 22:58 ` Steven Stallion
2020-01-03 23:38 Steven Stallion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fba80a0426a6f7b9feb9a45f813fc68f@gunge.quuxotic.net \
--to=sstallion@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).