Summary: | dev-libs/libgcrypt - .libs/libgcrypt.so: undefined reference to '__warn_memset_zero_len' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Current packages | Assignee: | Mikle Kolyada (RETIRED) <zlogene> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | crypto+disabled |
Priority: | Normal | Keywords: | UPSTREAM |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=578302 https://bugs.gentoo.org/show_bug.cgi?id=561938 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
random-drbg-dont-memset-zero.patch |
Description
Martin Mokrejš
2017-01-21 22:44:09 UTC
Created attachment 460842 [details]
build.log
Created attachment 461416 [details, diff]
random-drbg-dont-memset-zero.patch
(In reply to Kristian Fiskerstrand from comment #2) > Created attachment 461416 [details, diff] [details, diff] > random-drbg-dont-memset-zero.patch Can you try applying this patch (on a non-production-system, if it fixes the build error I'll upstream it to get a qualified opinion I'm not doing something stupid with the random number generator. Thank you, looks it is without errors and warnings now: /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I/scratch/var/tmp/portage/dev-libs/libgcrypt-1.7.5-r1/work/libgcrypt-1.7.5/random -I.. -I../src -I/scratch/var/tmp/portage/dev-libs/libgcrypt-1.7.5-r1/work/libgcrypt-1.7.5/src -O2 -pipe -maes -mpclmul -mpopcnt -mavx -march=native -fvisibility=hidden -Wall -c -o random-drbg.lo /scratch/var/tmp/portage/dev-libs/libgcrypt-1.7.5-r1/work/libgcrypt-1.7.5/random/random-drbg.c libtool: compile: x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I/scratch/var/tmp/portage/dev-libs/libgcrypt-1.7.5-r1/work/libgcrypt-1.7.5/random -I.. -I../src -I/scratch/var/tmp/portage/dev-libs/libgcrypt-1.7.5-r1/work/libgcrypt-1.7.5/src -O2 -pipe -maes -mpclmul -mpopcnt -mavx -march=native -fvisibility=hidden -Wall -c /scratch/var/tmp/portage/dev-libs/libgcrypt-1.7.5-r1/work/libgcrypt-1.7.5/random/random-drbg.c -fPIC -DPIC -o .libs/random-drbg.o It installed fine. (In reply to Martin Mokrejš from comment #4) > Thank you, looks it is without errors and warnings now: https://lists.gnupg.org/pipermail/gnupg-devel/2017-January/032502.html I ran into this same issue with 1.8.2. The attached patch worked for me. Since upstream decided not to include it, can we get a revbump with it attached? (In reply to Aaron W. Swenson from comment #6) > I ran into this same issue with 1.8.2. The attached patch worked for me. > > Since upstream decided not to include it, can we get a revbump with it > attached? That would mean we would have to carry it indefinitely, if you are interesting in having it applied, as a next step, could you please bring up the relevant discussion again upstream with some arguments for why it should be applied? (In reply to Kristian Fiskerstrand from comment #7) > (In reply to Aaron W. Swenson from comment #6) > > I ran into this same issue with 1.8.2. The attached patch worked for me. > > > > Since upstream decided not to include it, can we get a revbump with it > > attached? > > That would mean we would have to carry it indefinitely, if you are > interesting in having it applied, as a next step, could you please bring up > the relevant discussion again upstream with some arguments for why it should > be applied? Which gcc version are you using, or preferably a full emerge --info? as I recall this isn't an issue with newer versions of gcc |