From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-grpcio: correct asm for boringssl
Date: Wed, 17 Feb 2021 16:27:51 +0100 [thread overview]
Message-ID: <20210217152751.uxEtwIqqQXAkdM0qT9cIn7jHn-oFcGUWp61CWJS_XEE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28816@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/28816#issuecomment-780633831
Comment:
Thanks for catching this. In fact the change that broke the ASM patch seems to be all that was necessary for `GRPC_PYTHON_BUILD_SYSTEM_OPENSSL` to work properly with our LibreSSL. I'm going to check the new build against my gRPC stuff and see if everything works as expected.
next prev parent reply other threads:[~2021-02-17 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 13:27 [PR PATCH] " sgn
2021-02-17 14:53 ` ericonr
2021-02-17 14:53 ` ericonr
2021-02-17 15:27 ` ahesford [this message]
2021-02-17 15:32 ` [PR PATCH] [Closed]: " ahesford
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=20210217152751.uxEtwIqqQXAkdM0qT9cIn7jHn-oFcGUWp61CWJS_XEE@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).