Hi folks,
I'm looking to compile fips and openssl with gdb symbols. So far both 
compilations are unhappy with

make CFLAGS=-g

after doing my typical config stuff.

I noticed there are some "debug" options for fips/Configure, if you look really 
hard in the Configure file...I think these typically include a gdb flag. The 
problem is, if I do

cd fips
./Configure debug

on my build machine (which is gcc version 4.1.2) and then do

make

I get 

gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -
DOPENSSL_FIPSCANISTER -DBN_DEBUG -DREF_CHECK -DCONF_DEBUG -DBN_CTX_DEBUG -
DCRYPTO_MDEBUG -DOPENSSL_NO_ASM -ggdb -g2 -Wformat -Wshadow 
-Wmissing-prototypes 
-Wmissing-declarations -Werror   -c -o bn_blind.o bn_blind.c
gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -
DOPENSSL_FIPSCANISTER -DBN_DEBUG -DREF_CHECK -DCONF_DEBUG -DBN_CTX_DEBUG -
DCRYPTO_MDEBUG -DOPENSSL_NO_ASM -ggdb -g2 -Wformat -Wshadow 
-Wmissing-prototypes 
-Wmissing-declarations -Werror   -c -o bn_ctx.o bn_ctx.c
cc1: warnings being treated as errors
bn_ctx.c: In function ‘ctxdbg’:
bn_ctx.c:163: warning: cast from pointer to integer of different size
make[2]: *** [bn_ctx.o] Error 1
make[2]: Leaving directory `/home/cassie/fips-2.0/crypto/bn'
make[1]: *** [fips] Error 1
make[1]: Leaving directory `/home/cassie/fips-2.0/crypto'
make: *** [build_crypto] Error 1

which is an error I don't get if I just do a typical ./config.

I'm guessing this is a gcc version problem. But I'm wondering if there is any 
simpler way to get gdb symbols compiled into fips 2.0 and openssl 1.0.1c that 
I'm overlooking.

At the moment, I'm seeing odd failures in the MD4/MD4_Init functions and I 
can't 
debug them with gdb because I can't see what the source is doing.

Any advice is greatly appreciated. Thanks.

Cassie


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to