You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2020/04/23 10:08:00 UTC
[jira] [Commented] (ARROW-8565) [C++] Static build with AWS SDK
[ https://issues.apache.org/jira/browse/ARROW-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090463#comment-17090463 ]
Antoine Pitrou commented on ARROW-8565:
---------------------------------------
As far as I remember, this means that the AWS SDK build procedure will by default compile its own version of OpenSSL.
I would say it's probably fixable, but you will have to find out how and submit a PR for it :-)
> [C++] Static build with AWS SDK
> -------------------------------
>
> Key: ARROW-8565
> URL: https://issues.apache.org/jira/browse/ARROW-8565
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 0.17.0
> Reporter: Remi Dettai
> Priority: Major
> Labels: aws-s3, build-problem
>
> I can't find my way around the build system when using the S3 client.
> It seems that only shared target is allowed when the S3 feature is ON. In the thirdparty toolchain, when printing:
> ??FATAL_ERROR "FIXME: Building AWS C++ SDK from source will link with wrong libcrypto"??
> What is actually meant is that static build will not work, correct ? If it is the case, should libarrow.a be generated at all when S3 feature is on ?
> What can be done to fix this ? What does it mean that the SDK links to the wrong libcrypto ? Is it fixable ? Or is their a way to have the static build but maintain a dynamic link to a shared version of the SDK ?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)