segfault in gcrypt 1.4.0
Werner Koch
wk at gnupg.org
Mon Feb 25 14:31:16 CET 2008
On Fri, 22 Feb 2008 15:43, gnupg at ethen.de said:
> 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.
>From looking at the soruce that seems to be impossible. The __asm__
code is only used with padlock support configured. Please check whether
#define ENABLE_PADLOCK_SUPPORT 1
is enabled. It should not be if you used
./confgure --disable-padlock-support
Maybe I falsely suggested to use --disable-padlock which has no effect.
> 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
That is a different problem which happens only witout a frame pointer.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
More information about the Gcrypt-devel
mailing list