On Tue, 4 Jan 2005, Andy Polyakov wrote:

> Configure, openssl_fips_fingerprint, dbg_init and O_BINARY patches are 
> in now [both 0.9.7 and HEAD]. Compiler warnings will be addressed later. 
> As for -fno-strict-aliasing. I'd say it should rather be resolved in 
> source code, but [again] at some later point... A.

Using the new code in the 20050105 snapshots, I compiled under DJGPP,
using the 386 option and excluding idea, rc5, and mdc2. The 0.9.8
code and the 0.9.7 code (fips and non-fips) compile OK, with the fips
code stopping in "make test" at test_sha if "noise" isn't installed
to create /dev/urandom$. With "noise" installed, all three builds go
through "make test" OK, but the 0.9.8 version only installs one man
page in "make install" (man1/CA.pl.1), since the "set -e" prevents
installation of any additional pages.

Here are the warnings about lack of strict aliasing under the DJGPP
port of gcc. The warnings are the same for the 0.9.7 and 0.9.8 code
(except for pem_lib.c at line 483 in 0.9.8). I don't know how to fix
these in the source code myself, so I'll leave that to someone else
for a future patch.

a_type.c: In function `ASN1_TYPE_set':
a_type.c:74: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
x_name.c: In function `x509_name_ex_d2i':
x_name.c:171: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
x_name.c:177: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
x_name.c: In function `x509_name_encode':
x_name.c:239: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
x_name.c:242: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
pem_lib.c: In function `PEM_get_EVP_CIPHER_INFO':
pem_lib.c:481: warning: dereferencing type-punned pointer will break 
strict-aliasing rules

Thanks for working on my proposed patches so quickly.
                            Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to