On Thu, Jan 30, 2003 at 11:02:33AM +0100, Martin Witzel wrote: > This refers to 0.9.7. I have not verified it with earlier versions > > When I setup the build process with the 'config no-err' option, I get a lot > of _link_ errors in the apps directory, because the complete crypto/err > directory is skipped in the build process (compliments of 'Configure' which > modifies Makefile.org) and the applications which reference error functions > do not find them. [...] > There are two options to make no-err work: go over the apps code which > references error functions and exclude all references there when no-err is > on. Then the code in crypto/err may be safely excluded altogether during > the build process. OR correct the compiler switches in crypto/err to make > crypto/err compile and link some stripped down version of the error > routines; in this case we could leave the references to functions in > crypto/err in the apps code. The code which they call would not do much, > however.
Another option is to abandon no-err instead of trying to make it work ... some code systematically relies on the error queue being available (look for ERR_peek_error() and ERR_peek_last_error()). Do you think that there is a strong reason for keeping (and repairing) no-err? -- Bodo Möller <[EMAIL PROTECTED]> PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html * TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt * Tel. +49-6151-16-6628, Fax +49-6151-16-6036 ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
