R.K.Aa. wrote:
> i build on Linux with --enable-crypto and optimize=O2 > Clobbered today and saw a lot of warnings fly by when i rebuilt, > warnings I haven't really noticed earlyer. I realize the code hasn't > been changed in months, but does anyone recognize these? Were they > always there? What tag are you building from. I suspect that the number of Linux warings on the tip are quite large. We just landed a major change and are still stablizing the base. I doubt we are warning free on Solaris yet alone Linux (the latter tends to be more noisy than the former. > > Must have been thousands more - here some samples: > > > desblapi.c: In function `DES_CBCEn': > desblapi.c:100: warning: initialization discards qualifiers from pointer > target type > desblapi.c: In function `DES_CBCDe': > desblapi.c:121: warning: assignment discards qualifiers from pointer > target type > desblapi.c: In function `DES_EDE3CBCEn': > desblapi.c:137: warning: initialization discards qualifiers from pointer > target type > desblapi.c: In function `DES_EDE3CBCDe': > desblapi.c:160: warning: assignment discards qualifiers from pointer > target type > > > p12local.c: In function `sec_pkcs12_algtag_to_mech': > p12local.c:63: warning: enumeration value `SEC_OID_UNKNOWN' not handled > in switch These are pretty inocuous. Any switch statement on an algtag that doesn't have a default case in it will generate these warnings. Adding a 'default: break;' case gets rid of the warnings, but I only add them after I've determined that indeed all the rest of the cases should fall through the switch statement. > p12local.c:63: warning: enumeration value `SEC_OID_MD4' not handled in > switch >
