when emerge the current stable ebuild of libgcrypt with the xmerge script it fails because of linking to the wrong library (multilib issue) which was stated in this thread: http://lists.gnupg.org/pipermail/gcrypt-devel/2006-February/000925.html also some tests have to be tweaked (i think that's arch independent) for x86_64 i had to explicity disable asm to get it to work otherwise it'll lead to symbol issues during the build when linking libgcrypt.so i'm not too familar with ebuilds nor bug-reporting nor cross-compiling so i'll attach a patch for the ebuild and the libtool patch if anyone can confirm that i could supply patches for device-mapper lvm2 and cryptsetup-luks which also fail on x86_64....gnu to i386...uclibc Thanks for your time :)
Created attachment 111392 [details] ebuild patch for libgcrypt-1.2.2-r1
Created attachment 111394 [details, diff] libtool-cross-compile.patch
SpanKY: Is there any policy regarding this?
this isnt a libgcrypt specific issue and will be solved in a more general manner, so dont apply anything remotely like these patches to any of our ebuilds ...
