Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 04 Nov 2018 11:03:01 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 232954] devel/grpc: Not broken with OpenSSL 1.1
Message-ID:  <bug-232954-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232954

            Bug ID: 232954
           Summary: devel/grpc: Not broken with OpenSSL 1.1
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: vanilla@FreeBSD.org
          Reporter: brnrd@freebsd.org
          Assignee: vanilla@FreeBSD.org
             Flags: maintainer-feedback?(vanilla@FreeBSD.org)

Hi,

Whilst chasing removal of openssl-devel (moved to openssl111) I found
devel/grpc listed as BROKEN_SSL due to missing SSL_get0_next_proto_negotiat=
ed.
That was an issue with early versions of the openssl-devel port but that was
fixed in later versions.

I haven't built devel/grpc but from experience (www/nghttp2 and www/spdylay
have the same flags, see 232951 and 232952) I assume that these BROKEN_SSL =
can
be removed from the port. You're probably not receiving pkg-fallout messages
for 12 and head for the port either which is a good indication that it buil=
ds
with OpenSSL 1.1.1.

Cheers, Bernard.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232954-7788>