Hi,

Could you run cmake with -DCMAKE_FIND_DEBUG_MODE=ON and
share log of it?


FYI: Boost 1.76.0 is found in our CI:

  
https://github.com/apache/arrow/runs/5017148285?check_suite_focus=true#step:7:183

  -- Found Boost: /usr/local/lib/cmake/Boost-1.76.0/BoostConfig.cmake (found 
suitable version "1.76.0", minimum required is "1.64") found components: system 
filesystem 
  -- Boost include dir: /usr/local/include
  -- Boost libraries: Boost::system;Boost::filesystem


Thanks,
-- 
kou

In <CAGY9duW=utrsxvd+-uawh5jehzaaejj_exgtz6fhzvdnxpp...@mail.gmail.com>
  "Building Arrow Cpp: Cannot find Boost on MacOS" on Tue, 1 Feb 2022 16:18:13 
-0500,
  Li Jin <ice.xell...@gmail.com> wrote:

> Hello!
> 
> I am new to the Arrow cpp code and play with it a little. Unfortunately I
> hit this error when trying to cmake with preset "ninja-debug-basic". I
> wonder if anyone else has hit an similar issue?
> 
> cmake .. --preset ninja-debug-basic
> 
> ...
> 
> -- ARROW_ZSTD_BUILD_VERSION: v1.5.1
> 
> -- ARROW_ZSTD_BUILD_SHA256_CHECKSUM:
> dc05773342b28f11658604381afd22cb0a13e8ba17ff2bd7516df377060c18dd
> 
> CMake Error at
> /usr/local/Cellar/cmake/3.22.2/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230
> (message):
> 
>   Could NOT find Boost (missing: Boost_INCLUDE_DIR system filesystem)
> 
>   (Required is at least version "1.58")
> 
> Call Stack (most recent call first):
> 
>   
> /usr/local/Cellar/cmake/3.22.2/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594
> (_FPHSA_FAILURE_MESSAGE)
> 
>   /usr/local/Cellar/cmake/3.22.2/share/cmake/Modules/FindBoost.cmake:2375
> (find_package_handle_standard_args)
> 
>   cmake_modules/FindBoostAlt.cmake:41 (find_package)
> 
>   cmake_modules/ThirdpartyToolchain.cmake:241 (find_package)
> 
>   cmake_modules/ThirdpartyToolchain.cmake:956 (resolve_dependency)
> 
>   CMakeLists.txt:554 (include)
> 
> 
> I installed boost via HomeBrew under "/usr/local/Cellar/boost/1.76.0/" but
> I am not really familiar with where cmake looks for boost dependency..
> 
> 
> Much appreciated,
> 
> Li

Reply via email to