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?
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.
