segfault in gcrypt 1.4.0
gnupg at ethen.de
gnupg at ethen.de
Fri Feb 22 15:43:25 CET 2008
> Neiterh do I ;-). The bug report was not really clear on what you did.
> it looked like the library was build despite that a compile bug occurred.
No, this one wasn't.
> You may not use -fomit-frame-pointer with libgcrypt 1.4.0 on ia32. We
> have a fix in the works. Please describe the problem again you have
> compiling libgcrypt (rijndael.c?).
Without -fomit-frame-pointer I can't compile rijndael.c, no matter if I
use ./configure --disable-padlock or not. Please see my message 2008-02-13
12:58 MESZ.
If I set CFLAGS="-fomit-frame-pointer" for the whole libgcrypt-build I get
that segfault in gnupg, no matter if I use ./configure --disable-padlock or
not.
Hope that helps.
More information about the Gcrypt-devel
mailing list