On Tue, Jul 30, 2002 at 06:08:46PM +0300, Arne Ansper wrote:
attached is a patch for openssl-0.9.6e that removes the usage of die.
please review it carefully. all changes are localized but the action i
take in some places where error reporting is not possible might be little
bit wrong (i.e.
On Tue, Jul 30, 2002 at 06:08:46PM +0300, Arne Ansper wrote:
attached is a patch for openssl-0.9.6e that removes the usage of die.
please review it carefully. all changes are localized but the action i
take in some places where error reporting is not possible might be little
bit wrong (i.e.
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002 15:26:34
+0200 (METDST), Jeffrey Altman via RT [EMAIL PROTECTED] said:
rt Need to add it to the exports list.
For anyone who has the time, the fix is to move the declaration (but
not the macro die()) from cryptlib.h to crypto.h, then do a make
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
15:56:30 +0200 (CEST), Richard Levitte - VMS Whacker [EMAIL PROTECTED] said:
levitte In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
15:26:34 +0200 (METDST), Jeffrey Altman via RT [EMAIL PROTECTED] said:
levitte
levitte rt Need to add it to
On Tue, Jul 30, 2002 at 04:10:45PM +0200, Richard Levitte - VMS Whacker via RT wrote:
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
15:56:30 +0200 (CEST), Richard Levitte - VMS Whacker [EMAIL PROTECTED] said:
levitte In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
15:26:34 +0200
Lutz Jaenicke via RT wrote:
On Tue, Jul 30, 2002 at 04:10:45PM +0200, Richard Levitte - VMS Whacker via RT wrote:
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
15:56:30 +0200 (CEST), Richard Levitte - VMS Whacker [EMAIL PROTECTED] said:
levitte In message [EMAIL PROTECTED] on Tue, 30 Jul
OK, I don't understand why it needs to be exported - isn't it internal
to the library? But assuming it does, I prefer the original suggestions
(i.e. move the declaration of OpenSSLDie()).
It needs to be exported because the function is defined in
libeay32.dll and used in ssleay32.dll on
OK, I don't understand why it needs to be exported - isn't it internal
to the library? But assuming it does, I prefer the original suggestions
(i.e. move the declaration of OpenSSLDie()).
It needs to be exported because the function is defined in
libeay32.dll and used in ssleay32.dll on
On Tue, Jul 30, 2002 at 03:26:34PM +0200, Jeffrey Altman via RT wrote:
Need to add it to the exports list.
I just had a look into this thing.
Ben designed the die() function such that it uses cryptlib.h, which is
not exported. Thus the macro die() and the underlying OpenSSLDie() function
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002 15:26:34
+0200 (METDST), Jeffrey Altman via RT [EMAIL PROTECTED] said:
rt Need to add it to the exports list.
For anyone who has the time, the fix is to move the declaration (but
not the macro die()) from cryptlib.h to crypto.h, then do a make
I have added Ben to the CCs of this ticket, as it might affect all other
patches, too!
btw, i'm in process of rewriting the patches to not use die at all.
openssl-0.9.5a is almost ready.
arne
__
OpenSSL Project
rt Need to add it to the exports list.
For anyone who has the time, the fix is to move the declaration (but
not the macro die()) from cryptlib.h to crypto.h, then do a make
update.
And this will auto-generate the entry for util/libeay.num ? Cool.
Jeffrey Altman * Sr.Software Designer
btw, i'm in process of rewriting the patches to not use die at all.
openssl-0.9.5a is almost ready.
i started with openssl-0.9.6e instead.
attached is a patch for openssl-0.9.6e that removes the usage of die.
please review it carefully. all changes are localized but the action i
take in
jaltman Now the choices as I see it are:
jaltman
jaltman . export the function. which I have done in order to get the
jaltmancode to compile and link on Windows, or
jaltman
jaltman . remove the call entirely and instead simply have OpenSSL return
jaltmanan error to the
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002 15:49:00 +0100, Ben
Laurie [EMAIL PROTECTED] said:
ben OK, I don't understand why it needs to be exported - isn't it internal
ben to the library? But assuming it does, I prefer the original suggestions
ben (i.e. move the declaration of
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002 15:49:00 +0100, Ben
Laurie [EMAIL PROTECTED] said:
ben OK, I don't understand why it needs to be exported - isn't it internal
ben to the library? But assuming it does, I prefer the original suggestions
ben (i.e. move the declaration of
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
10:56:29 EDT, Jeffrey Altman [EMAIL PROTECTED] said:
jaltman
jaltman OK, I don't understand why it needs to be exported - isn't it internal
jaltman to the library? But assuming it does, I prefer the original suggestions
jaltman (i.e. move
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
10:56:29 EDT, Jeffrey Altman [EMAIL PROTECTED] said:
jaltman
jaltman OK, I don't understand why it needs to be exported - isn't it internal
jaltman to the library? But assuming it does, I prefer the original suggestions
jaltman (i.e. move
jaltman Now the choices as I see it are:
jaltman
jaltman . export the function. which I have done in order to get the
jaltmancode to compile and link on Windows, or
jaltman
jaltman . remove the call entirely and instead simply have OpenSSL return
jaltmanan error to the
Lutz Jaenicke via RT wrote:
On Tue, Jul 30, 2002 at 04:10:45PM +0200, Richard Levitte - VMS Whacker via RT wrote:
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
15:56:30 +0200 (CEST), Richard Levitte - VMS Whacker [EMAIL PROTECTED] said:
levitte In message [EMAIL PROTECTED] on Tue, 30 Jul
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
11:31:17 EDT, Jeffrey Altman [EMAIL PROTECTED] said:
jaltman since they do not compile on two major platforms.
On VMS, creating OpenSSL shared libraries is not the norm yet, so
it'll build fine :-).
--
Richard Levitte \ Spannvägen 38, II \
In message [EMAIL PROTECTED] on Tue, 30 Jul 2002
16:16:50 EDT, Jeffrey Altman [EMAIL PROTECTED] said:
jaltman fine. shared libraries won't work on two major platforms.
jaltman One of which where it is the norm.
I'm not arguing that.
jaltman the other bug I submitted this morning prevents the
In message [EMAIL PROTECTED] on Tue, 30 Jul
2002 11:31:17 EDT, Jeffrey Altman [EMAIL PROTECTED] said:
jaltman since they do not compile on two major platforms.
On VMS, creating OpenSSL shared libraries is not the norm yet, so
it'll build fine :-).
fine. shared libraries won't work on
In message [EMAIL PROTECTED] on Tue, 30 Jul
2002 11:31:17 EDT, Jeffrey Altman [EMAIL PROTECTED] said:
jaltman since they do not compile on two major platforms.
On VMS, creating OpenSSL shared libraries is not the norm yet, so
it'll build fine :-).
fine. shared libraries won't work on
24 matches
Mail list logo
