Summary: | app-crypt/heimdal-7.8.0-r3: libheimsqlite3.so has conflicting symbols with libsqlite3.so, leading to application crashes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marco Rebhan <me> |
Component: | Current packages | Assignee: | Gentoo Kerberos Maintainers <kerberos> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | base-system, jsmolic, me |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info sqlite
lldb dolphin lldb quassel emerge --info heimdal heimdal config.log |
Description
Marco Rebhan
2025-01-26 19:43:20 UTC
Created attachment 917569 [details]
emerge --info sqlite
Created attachment 917570 [details]
lldb dolphin
Created attachment 917571 [details]
lldb quassel
I figured out what this is actually caused by. It's caused by app-crypt/heimdal. heimdal builds libheimsqlite3.so which ends up getting linked into applications along with the real sqlite3 when they link to libkrb5, leading to conflicting symbols. related: https://github.com/heimdal/heimdal/issues/1142 This is clearly unintended since the Heimdal ebuild already passes --with-sqlite3="${EPREFIX}"/usr to configure, but the configure script detects it as not present. A workaround is setting EXTRA_ECONF="--with-sqlite3-lib=/usr/lib64/libsqlite3.so --with-sqlite3-headers=/usr/include" when building Heimdal. Created attachment 920110 [details]
emerge --info heimdal
Created attachment 920111 [details]
heimdal config.log
|