Date: Wed, 28 Jun 2017 13:50:41 -0400 From: Steve Wills <steve@mouf.net> To: Torsten Zuehlsdorff <tz@FreeBSD.org>, Matthias Fechner <idefix@fechner.net>, ruby@freebsd.org Subject: Re: Help needed: net/rubygem-grpc Message-ID: <1d1c9ced-a473-ff50-06c0-ea9ae7f2032a@mouf.net> In-Reply-To: <2369ae1e-30cb-52d7-6697-a99139d74479@mouf.net> References: <4474b97e-88ec-ead8-bb13-79e5889bf237@FreeBSD.org> <b74007b8-02f7-0b58-7618-cc006074a6e1@mouf.net> <c5c542e2-c667-67b8-ec7b-6dd07069aa91@fechner.net> <bf97c60e-2076-cf5b-b587-48b978fdf51f@FreeBSD.org> <2369ae1e-30cb-52d7-6697-a99139d74479@mouf.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --uRIWQ2vCUfKLav9ngcvwhFFH3FL91XPvA Content-Type: multipart/mixed; boundary="Ff8oDMojfmLOuFNptQV1PIF2iVPFoiXOO"; protected-headers="v1" From: Steve Wills <steve@mouf.net> To: Torsten Zuehlsdorff <tz@FreeBSD.org>, Matthias Fechner <idefix@fechner.net>, ruby@freebsd.org Message-ID: <1d1c9ced-a473-ff50-06c0-ea9ae7f2032a@mouf.net> Subject: Re: Help needed: net/rubygem-grpc References: <4474b97e-88ec-ead8-bb13-79e5889bf237@FreeBSD.org> <b74007b8-02f7-0b58-7618-cc006074a6e1@mouf.net> <c5c542e2-c667-67b8-ec7b-6dd07069aa91@fechner.net> <bf97c60e-2076-cf5b-b587-48b978fdf51f@FreeBSD.org> <2369ae1e-30cb-52d7-6697-a99139d74479@mouf.net> In-Reply-To: <2369ae1e-30cb-52d7-6697-a99139d74479@mouf.net> --Ff8oDMojfmLOuFNptQV1PIF2iVPFoiXOO Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi again, Doing some testing on this, I'm running into an issue: /usr/local/lib/libgrpc.so.1: Undefined symbol "OpenSSL_add_all_algorithms= " This looks to be an issue with libgrpc, not an issue with the gem itself, but I'm not sure yet. I'll investigate more. I may not be able to avoid using the bundled boringssl as long as grpc is using it's bundled boringssl (which I think it should not do, but it does currently do). Steve On 06/28/2017 13:03, Steve Wills wrote: > Hi, >=20 > On 06/28/2017 11:54, Torsten Zuehlsdorff wrote: >> >> >> On 28.06.2017 17:41, Matthias Fechner wrote: >>> Hi Steve, >>> >>> >>> regarding the comment here: >>> https://gitlab.com/gitlab-org/gitaly/issues/154#note_33314534 >>> >>> I think gitlab should work with version 1.4.0, but I think a test is >>> always a good idea. >> >=20 > Ok, sounds good. >=20 >> Thanks for your time Steve! To add something to Matthias comment: ther= e >> is already a devel/grpc port, which seems to be very similar to the >> needed rubygem. Maybe this could help us? >=20 > Yeah, I've updated the port to use the grpc from the port instead of th= e > bundled one. See attached (let me know if it doesn't come through). > There's still at least one problem with this because I'm also removing > the bundled ssl certs. I think it should use the ones from ca_root_nss > instead, I'm working on that. But first I want to figure out how to run= > the tests and that's taking a little extra time because the Gemfile > isn't included with the gem itself. Also, I'm sure the grpc developers > would consider this all wrong, but for us I think it's the right path. >=20 > Steve >=20 --Ff8oDMojfmLOuFNptQV1PIF2iVPFoiXOO-- --uRIWQ2vCUfKLav9ngcvwhFFH3FL91XPvA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGjBAEBCgCNFiEEmPpBSlwqDvnP0K0N9c9isyB7G6EFAllT7HFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk4 RkE0MTRBNUMyQTBFRjlDRkQwQUQwREY1Q0Y2MkIzMjA3QjFCQTEPHHN0ZXZlQG1v dWYubmV0AAoJEPXPYrMgexuhVK4H+wb631J4MzbCJZJ/ebr7c34eqClWtl4WcgH8 A5G+mN6Szu6Kl0WyYxdfCATS6LnnRLHpmJRweBUQHmR1llHYuWJttbJwc0EGVMTm 8ykTjFYvOTMrHdlFNfz4YPFe1sTk1bFXcUK/GtMNj+5HYs32c1iFKJV5SCObkrIl BErdBBoQPVxdMejPxgTw00eTeJg0zVC24Pevvpd7sPEeWXWM7izeCSF8HyzJF+DX linuvmld0usauMPIYxrkJUXSXVTpy+cBZz9pwM+Wt1bK/tnGnbCv97470X6SIsIf q4sqDwkWSDdp4x1Zo9VI/g0+hS01dWbCYqszpgJbE2LdQ7EeJTc= =k9HG -----END PGP SIGNATURE----- --uRIWQ2vCUfKLav9ngcvwhFFH3FL91XPvA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1d1c9ced-a473-ff50-06c0-ea9ae7f2032a>