| Summary: | app-crypt/p11-kit: broken symbol versioning with llvm-core/lld-17 (app-crypt/pinentry fails to build with llvm-lld-17: ...) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | topological-automata <safeguard_502> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | ezzieyguywuf, lockalsash, marcin.deranek, safeguard_502 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=937990 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 912821 | ||
| Attachments: |
app-crypt/pinentry's build.log
emerge --info pinentry's build.log after rebuilding (successfully) app-crypt/{gcr,p11-kit} |
||
Created attachment 875444 [details]
emerge --info
emerge --info
The issue is in p11-kit. Is p11-kit-0.25.3 any better? Rebuilding app-crypt/gcr-3.41.1-r2 fixed this issue for me. apologies for late response; I can't get bugzilla to send me mails when someone comments on the issues; > Is p11-kit-0.25.3 any better? nope, tried to build Is p11-kit-0.25.3-r2; it builds fine, but pinentry still gives out the same error attached at the beginning, but you can find another build.log for good measure attached now. > Rebuilding app-crypt/gcr-3.41.1-r2 fixed this issue for me. I tried rebuilding app-crypt/gcr-3.41.1-r2 and pinentry still has that error, so no luck Created attachment 880794 [details]
pinentry's build.log after rebuilding (successfully) app-crypt/{gcr,p11-kit}
I was able to successfully install pinentry after first reinstall p11-kit with gcc instead of clang A similar error is emitted when app-crypt/p11-kit is built with sys-devel/mold. When app-crypt/p11-kit is built using the default linker (bfd) everything works just fine. If I understand correctly, this also breaks compilation of gnome-base/gnome-control-center-45.3, which fails with:
> /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libgck-1.so: undefined reference to `p11_kit_uri_any_unrecognized@LIBP11_KIT_1.0'
> /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libgck-1.so: undefined reference to `p11_kit_uri_free@LIBP11_KIT_1.0'
> /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libgck-1.so: undefined reference to `p11_kit_uri_get_attributes@LIBP11_KIT_1.0'
...
(where libgck-1.so comes from app-crypt/gcr-3.41.1-r2)
In this case compilation issue of gnome-base/gnome-control-center-45.3 is fixed by compiling app-crypt/p11-kit with gcc.
|
Created attachment 875443 [details] app-crypt/pinentry's build.log attached is build.log and emerge --info. heard that `--no-allow-shlib-undefined` in llvm 17's lld, is now the default and it breaks many packages, so my question is: is the problem directly upstream?