> Sometime in the last few months, changes were made to e_os2.h in > the stable 0.9.8 series, which broke the DJGPP build. It looks > like a cleanup was made, removing OPENSSL_SYSNAME_WIN16, but the > OPENSSL_SYSNAME_MSDOS code appears to have been accidentally removed. > I see that none of the platforms generate OPENSSL_SYSNAME_WIN16 in > Configure, but there are still lots of places in the code that refer > to it. Do we really want to remove OPENSSL_SYSNAME_WIN16 from e_os2.h?
Yes, because it's plain deceptive. > Is it clear that no on is going to use that part of the code again? Is there a *shred* of evidence that [any recent version of] OpenSSL has [ever] worked on any 16-bit platform? > The patch reverts e_os2.h to what it was a few months ago. If you > only want to put the MSDOS code back in, rather than restore it all, http://cvs.openssl.org/chngview?cn=14710 > When reviewing my log files, I noted two directories where "make > depend" doesn't use the CFLAG. It looked like something to be fixed. > Is there a reason to omit CFLAG only in these two directories? Not that I know of. http://cvs.openssl.org/chngview?cn=14712. > I haven't had a chance to try to compile the current HEAD code yet. Please do (as it's getting more aggressive on WIN16:-). Thanks for report. Case is being dismissed. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
