[
https://issues.apache.org/jira/browse/ARROW-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610415#comment-17610415
]
Joris Van den Bossche commented on ARROW-6459:
----------------------------------------------
As Alenka mentioned above as well, at the moment you still need "a" Python
available on your system when building Arrow C++, because the cmake files look
for Python for the lint targets (and AFAIK this is always done, and you can't
turn this off. But maybe we should change this and make this optional?)
As long as Python is required to build C++, I think it makes sense to keep
Python in the conda env.
> [C++] Remove "python" from conda_env_cpp.txt
> --------------------------------------------
>
> Key: ARROW-6459
> URL: https://issues.apache.org/jira/browse/ARROW-6459
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Assignee: Alenka Frim
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> I'm not sure why "python" is in this dependency file -- if it is used to
> maintain a toolchain external to a particular Python environment then it
> confuses CMake like
> {code}
> CMake Warning at cmake_modules/BuildUtils.cmake:529 (add_executable):
> Cannot generate a safe runtime search path for target arrow-python-test
> because there is a cycle in the constraint graph:
> dir 0 is [/home/wesm/code/arrow/cpp/build/debug]
> dir 1 is [/home/wesm/miniconda/envs/arrow-3.7/lib]
> dir 2 must precede it due to runtime library [libcrypto.so.1.1]
> dir 2 is [/home/wesm/cpp-toolchain/lib]
> dir 1 must precede it due to runtime library [libpython3.7m.so.1.0]
> Some of these libraries may not be found correctly.
> Call Stack (most recent call first):
> src/arrow/CMakeLists.txt:52 (add_test_case)
> src/arrow/python/CMakeLists.txt:139 (add_arrow_test)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
