[
https://issues.apache.org/jira/browse/KUDU-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith updated KUDU-3804:
--------------------------------
Description: After updating Kudu to master, trying to use it in Impala
results in a crash on library load because of conflicts between protobuf
versions. This is supposed to be handled by symbols.map and
--exclude-libs=libprotobuf, but after
[https://github.com/apache/kudu/commit/1d789a87a] we start to link with {{lld}}
in Impala's native-toolchain while the rest uses {{{}gold{}}}. Reverting that
patch avoids this issue. So there seems to be some conflict if we use lld for
Kudu and gold for Impala. (was: After Kudu moved to protobuf 3.21.9, trying to
use it in Impala results in a crash on library load because of conflicts with
Impala's protobuf 3.14.0.
[https://github.com/apache/kudu/blob/master/src/kudu/client/symbols.map#L32]
claims to handle preventing protobuf exports, but is incomplete.)
> Kudu symbol mapping for protobuf is incomplete
> ----------------------------------------------
>
> Key: KUDU-3804
> URL: https://issues.apache.org/jira/browse/KUDU-3804
> Project: Kudu
> Issue Type: Bug
> Components: build
> Affects Versions: 1.19.0
> Reporter: Michael Smith
> Priority: Major
>
> After updating Kudu to master, trying to use it in Impala results in a crash
> on library load because of conflicts between protobuf versions. This is
> supposed to be handled by symbols.map and --exclude-libs=libprotobuf, but
> after [https://github.com/apache/kudu/commit/1d789a87a] we start to link with
> {{lld}} in Impala's native-toolchain while the rest uses {{{}gold{}}}.
> Reverting that patch avoids this issue. So there seems to be some conflict if
> we use lld for Kudu and gold for Impala.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
