FS#73311 - [libetebase] symbol lookup error at libetebase.so: undefined symbol
Attached to Project:
Arch Linux
Opened by Outvi V (outloudvi) - Sunday, 09 January 2022, 17:49 GMT
Last edited by Antonio Rojas (arojas) - Monday, 10 January 2022, 07:21 GMT
Opened by Outvi V (outloudvi) - Sunday, 09 January 2022, 17:49 GMT
Last edited by Antonio Rojas (arojas) - Monday, 10 January 2022, 07:21 GMT
|
Details
Description:
/usr/bin/akonadi_etesync_resource: symbol lookup error: /usr/lib/libetebase.so.0: undefined symbol: crypto_aead_xchacha20poly1305_ietf_encrypt_detached A rebuild of `libetebase` fixes it. Additional info: - package version(s): * extra/kdepim-runtime 21.12.1-1 * extra/libetebase 0.5.1-1 Steps to reproduce: 1. `pacman -S libetebase kdepim-runtime` 2. Run `/usr/bin/akonadi_etesync_resource` |
This task depends upon
Closed by Antonio Rojas (arojas)
Monday, 10 January 2022, 07:21 GMT
Reason for closing: Fixed
Additional comments about closing: libetebase 0.5.1-2, thanks @loqs
Monday, 10 January 2022, 07:21 GMT
Reason for closing: Fixed
Additional comments about closing: libetebase 0.5.1-2, thanks @loqs
I was building the package on my own system with:
* asp update
* asp export etebase
* cd etebase
* makepkg .
It appears when using LTO the statically built libsodium used by the rust crate libsodium-sys leaves some symbols undefined.
Diabling LTO seems to avoid the issue. The system's libsodium could be used by building with SODIUM_USE_PKG_CONFIG= make
Yes, I have !lto in my OPTIONS.