[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-02-08 Thread jablko
Github user jablko commented on the issue: https://github.com/apache/trafficserver/pull/1388 Merged. Thanks @zwoop! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-02-01 Thread jablko
Github user jablko commented on the issue: https://github.com/apache/trafficserver/pull/1388 @zwoop I separated the commits because they each address a different issue -- #1384 and #1385. I think that makes the most sense ... but I'm happy to squash them if you prefer! --- If your

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-31 Thread atsci
Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1388 clang-analyzer build *successful*! See https://ci.trafficserver.apache.org/job/Github-Clang/11/ for details. --- If your project is set up for it, you can reply to this email and have

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-31 Thread atsci
Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1388 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1446/ for details. --- If your project is set up for it, you can reply to this email and have

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-31 Thread atsci
Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1388 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/1339/ for details. --- If your project is set up for it, you can reply to this email and have your

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-31 Thread zwoop
Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/1388 @jablko do we need two commits here? Or can they be squashed? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-31 Thread zwoop
Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/1388 [approve ci] to get the clang-analyzer build --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-28 Thread atsci
Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1388 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/1308/ for details. --- If your project is set up for it, you can reply to this email and have your

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-28 Thread atsci
Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1388 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1415/ for details. --- If your project is set up for it, you can reply to this email and have

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-28 Thread atsci
Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1388 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1414/ for details. --- If your project is set up for it, you can reply to this email and have

[GitHub] trafficserver issue #1388: Fixes for building with OpenSSL 1.1

2017-01-28 Thread atsci
Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1388 Linux build *failed*! See https://ci.trafficserver.apache.org/job/Github-Linux/1307/ for details. --- If your project is set up for it, you can reply to this email and have your reply