You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/03/15 05:34:38 UTC

[jira] [Commented] (TS-3443) Configure openssl tls1.h detection faulty

    [ https://issues.apache.org/jira/browse/TS-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362199#comment-14362199 ] 

Leif Hedstrom commented on TS-3443:
-----------------------------------

Can you comment with some more details on your setup? We build on a large number of platforms, with no problems. See the current builds at https://ci.trafficserver.apache.org (none of them have build issues with TLS). The errors that are there currently are known, I'm investigating right now, but are definitely not related to TLS in any way.

> Configure openssl tls1.h detection faulty
> -----------------------------------------
>
>                 Key: TS-3443
>                 URL: https://issues.apache.org/jira/browse/TS-3443
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Build
>            Reporter: Felix Buenemann
>             Fix For: sometime
>
>
> The configure check for tls1.h fails, because at least on openssl 1.0.2 tls1.h depends on a macro from openssl/safestack.h.
> I've created [pull request #180 on github|https://github.com/apache/trafficserver/pull/180] to fix the detection by including openssl/ssl.h in the configure check, which in turn includes safestack.h. Given that ssl.h is already required that solution should be fully backwards compatible to older versions that might not require safestack.h.
> This problem affects at least master and 5.2.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)