You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@zookeeper.apache.org by GitBox <gi...@apache.org> on 2019/11/22 05:51:22 UTC

[GitHub] [zookeeper] ztzg commented on issue #1107: ZOOKEEPER-2122: add SSL support for C-client

ztzg commented on issue #1107: ZOOKEEPER-2122: add SSL support for C-client
URL: https://github.com/apache/zookeeper/pull/1107#issuecomment-557399890
 
 
   I experienced [a failed build](https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build-maven/1633/) with this error:
   
        configure: error: --with-openssl path does not point to a directory
        [ERROR] Command execution failed.
   
   It seems that this stanza (in `pom.xml`) is not valid on all build hosts:
   
       <argument>--with-openssl=/usr/include/openssl/</argument>
   
   Not sure how we can make sure that OpenSSL headers are installed on all Jenkins workers?
   
   It might also be nice to use autodetection, at least for `autoconf`; here is what I ended up with in v2 of the SASL patches (comments welcome; I'm trying to "align" the two features):
   
   https://github.com/apache/zookeeper/blob/f248c53089d82d2372404f0a7ca992bebd6ecf68/zookeeper-client/zookeeper-client-c/configure.ac#L114-L142

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services