Created attachment 712743 [details] build log I'm unable to compile libgcrypt with a clang toolchain and i suspect it's because a lack of compatibility because a #pragma line in the codebase in random/jitterentropy-base.c. Is this a bug of clang or am i intended to compile libgcrypt with a gcc toolchain exclusively? Thank you for your time
Created attachment 712746 [details] config log
Created attachment 712749 [details] emerge info
Created attachment 712752 [details] emerge pqv
An overlay has it patched here: https://github.com/BilyakA/gentoo-clang/blob/master/dev-libs/libgcrypt/files/libgcrypt-1.8.5-clang.patch
Could you report this upstream?
(In reply to Sam James from comment #5) > Could you report this upstream? I found the bugs webpage in the git AUTHORS file, I'll try to report and then i'll post the bug url here for easy access
(In reply to vicalcas from comment #6) > (In reply to Sam James from comment #5) > > Could you report this upstream? > > I found the bugs webpage in the git AUTHORS file, I'll try to report and > then i'll post the bug url here for easy access Thank you! :)
The promised bug url is here: https://dev.gnupg.org/T5457
As suggested in the bug tracker the problem is that with clang the USE flag o-flag-munging has to be enabled in order for clang to compile it. I will leave up to you if this has to be closed or the ebuild has to be modified, but the bottom line is that if that flag is enabled clang doesn't complain and compiles it. Not considering that flag was an error on my end and i'm sorry for it