[
https://issues.apache.org/jira/browse/ORC-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17986159#comment-17986159
]
Will Ayd commented on ORC-1940:
-------------------------------
For some more context, the protobuf that Apache Arrow installs in its CI is
version 3.21.2. As you can see in the git blame, that pkg-config file does not
provide anything around threads as a dependency for its downstream projects:
[https://github.com/protocolbuffers/protobuf/blob/839b18b1ba42639fedecfd751102afcc5736b5d4/protobuf.pc.in#L9]
(more recent versions of protobuf would provide this, as well as Meson source
dependencies)
> Meson configuration should add thread dependency to orc lib
> -----------------------------------------------------------
>
> Key: ORC-1940
> URL: https://issues.apache.org/jira/browse/ORC-1940
> Project: ORC
> Issue Type: Bug
> Reporter: Will Ayd
> Priority: Minor
>
> When using orc as a dependency of Apache Arrow, I received some errors around
> symbols exported by thread that are missing. You can see an example of this
> in the Arrow CI:
> [https://github.com/apache/arrow/actions/runs/15878114506/job/44770826425?pr=46906#step:6:1669]
> I do find this a bit strange, as orc does not appear to directly use it.
> Additionally, the protobuf library that orc uses as a dependency provides
> this when compiled from source. However, my guess is on platforms where
> protobuf is system-installed, it may not be correctly identifying via
> pkg-config that downstream users should be using threads.
> In any case, the CMake configuration seems to globally require it, so we can
> do it in the Meson configuration as well
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
