h-vetinari commented on issue #33882: URL: https://github.com/apache/arrow/issues/33882#issuecomment-1405966845
> Hmm. It's strange. It's happen in https://github.com/apache/arrow/blob/master/cpp/cmake_modules/ThirdpartyToolchain.cmake#L288-L305 . > > Can we add debug logs (`message(...)`) in the block or enable something general CMake's debug log to debug this? That code is really hard to understand. I'm happy to try with a patch, but not sure what/where. Just now I got worried because on linux, pkg-config claims to find a static grpc++ somehwere, though the build coming in through conda-forge [definitely](https://github.com/regro/libcfgraph/blob/master/artifacts/libgrpc/conda-forge/linux-64/libgrpc-1.51.1-h30feacc_0.json#L513-L548) does not contain any static libs. However, it looks like that's just the log-message being unaware of which flavour of dynamic/static is actually being found by pkg-config. Can we just disable the whole pkg-config search completely? Our builds have CMake metadata, and `find_package(${PACKAGE_NAME} REQUIRED)` should work in the vast majority of cases (even moreso with `CONFIG` mode), and especially for gprc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
