Orc unable to find dependencies, even when they exist
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake
- Domain
- build-system
Research direction
Reproduce the conda setup with the minimal CMakeLists.txt and compare the two find_package calls. Start with lib/cmake/orc/FindSnappy.cmake and lib/cmake/orc/orcConfig.cmake, using the reported CMake dependency call stack as the entry point. Done means find_package(orc REQUIRED) succeeds while resolving the existing Snappy installation.
Written by the indexing model from the issue text.
Description
To reproduce the issue you can create a conda environment with orc and a third party dependency, like Snappy:
$ conda create -n foo orc snappy
$ conda activate foo
With the minimal CMake project below, no errors occur during setup:
cmake_minimum_required(VERSION 3.2)
project(foo)
find_package(Snappy REQUIRED)
However, if you add a call to find orc, you will then get an error that Snappy could not be found:
cmake_minimum_required(VERSION 3.2)
project(foo)
find_package(Snappy REQUIRED)
find_package(orc REQUIRED)
$ cmake -S . -B build
-- SNAPPY_HOME:
CMake Error at /home/will/miniforge3/envs/foo/lib/cmake/orc/FindSnappy.cmake:80 (message):
Could not find Snappy in system search paths.
Call Stack (most recent call first):
/usr/share/cmake-3.31/Modules/CMakeFindDependencyMacro.cmake:76 (find_package)
/home/will/miniforge3/envs/foo/lib/cmake/orc/orcConfig.cmake:72 (find_dependency)
CMakeLists.txt:5 (find_package)
This issue was first discovered downstream in Apache Arrow (see https://github.com/apache/arrow/pull/46906#issuecomment-3286997441) and appears to have started with Orc 2.1.0
- Dominant language
- Java
- Stars
- 769
- Forks
- 515
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/orc
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
cross compileOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grimmory-tools/grimmory#2850 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·
-
Update license yearOpen0 - Backlog 1 - Ready documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100