Hi Kou,

I'm attaching the cmake log files for the same command with both 
PYARROW_CMAKE_OPTIONS and CMAKE_PREFIX_PATH set and exported as requested.


Thanks,
Yaron.
________________________________
From: Sutou Kouhei <k...@clear-code.com>
Sent: Sunday, September 11, 2022 6:03 PM
To: dev@arrow.apache.org <dev@arrow.apache.org>
Subject: Re: PyArrow build problem

Hi,

It seems that
/miniconda3/envs/pyarrow-dev/lib/cmake/Arrow/ArrowConfig.cmake
isn't used. Could you share a build log with
PYARROW_CMAKE_OPTIONS="-DCMAKE_FIND_DEBUG_MODE=ON" environment
variable?

You may need to export
CMAKE_PREFIX_PATH=/miniconda3/envs/pyarrow-dev environment
variable but the path should be included in
the CMAKE_SYSTEM_PREFIX_PATH CMake variable via the CONDA_PREFIX
environment variable...:
https://cmake.org/cmake/help/latest/variable/CMAKE_SYSTEM_PREFIX_PATH.html


Thanks,
--
kou

In
 <paxp190mb156524af6c6ea47b8faa08fdbd...@paxp190mb1565.eurp190.prod.outlook.com>
  "PyArrow build problem" on Sun, 11 Sep 2022 13:57:53 +0000,
  Yaron Gvili <rt...@hotmail.com> wrote:

> Hi All,
>
> I got the error below while running "cd python/ && python setup.py build_ext 
> --inplace", after successfully building and installing a recent master 
> version (a63e60bad89b41266d155bc496eb383765702492) of Arrow C++ under a 
> pyarrow-dev Conda environment, as in the Python dev doc 
> (https://arrow.apache.org/docs/developers/python.html). I didn't have a 
> problem with this environment until now. Anyone have an idea how to fix the 
> error?
>
> CMake Error at 
> /miniconda3/envs/pyarrow-dev/lib/cmake/Parquet/ParquetConfig.cmake:65 
> (arrow_keep_backward_compatibility):
>   Unknown CMake command "arrow_keep_backward_compatibility".
> Call Stack (most recent call first):
>   
> /miniconda3/envs/pyarrow-dev/share/cmake-3.23/Modules/CMakeFindDependencyMacro.cmake:47
>  (find_package)
>   
> /miniconda3/envs/pyarrow-dev/lib/cmake/ArrowDataset/ArrowDatasetConfig.cmake:55
>  (find_dependency)
>   CMakeLists.txt:123 (find_package)
>
>
> Cheers,
> Yaron.

Reply via email to