You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Wes McKinney (Jira)" <ji...@apache.org> on 2021/02/20 03:30:00 UTC
[jira] [Commented] (ARROW-5280) [C++] Find a better solution to the
conda compilers macOS issue
[ https://issues.apache.org/jira/browse/ARROW-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287480#comment-17287480 ]
Wes McKinney commented on ARROW-5280:
-------------------------------------
This problem doesn't seem to have a resolution now in 2021. I suggest we close and direct users to follow the Anaconda documentation if they are using the conda compiler toolchain
> [C++] Find a better solution to the conda compilers macOS issue
> ---------------------------------------------------------------
>
> Key: ARROW-5280
> URL: https://issues.apache.org/jira/browse/ARROW-5280
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Developer Tools
> Reporter: Neal Richardson
> Priority: Major
>
> See [https://github.com/apache/arrow/pull/4231#pullrequestreview-234617308] and https://issues.apache.org/jira/browse/ARROW-4935. Conda's `compilers` require an old macOS SDK, which makes installation awkward at best. We can _almost_ build on macOS without conda `compilers`, but the jemalloc failure remains. As Uwe says, "Maybe we can figure out a way in conda-forge to use newer compilers than the ones referenced by the {{compilers}} package."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)