Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Fri, Jan 10, 2003 at 07:27:35PM +0100, Corinna Vinschen wrote:
[...]
Hi, I have chosen another packaging method:
Version 0.9.6h will consist only of the needed DLLs to link applications
build against it.
The package will be called
openssl096-0.9.6h-1.tar.bz2
The new 0.9.7 version will become the openssl package again, as the
0.9.6 version before. So the new packages are still just called
openssl:
openssl-0.9.7-1.tar.bz2
openssl-devel-0.9.7-1.tar.bz2
openssl-0.9.7-1-src.tar.bz2
That means, the patch to util/cygwin.sh can be reverted to create
the normal openssh packages again instead of openssh2.
Is that ok with you? Would you revert the cygwin.sh patch then?
Hi,
in the meantime I released Cygwin's openssl using the above packaging
scheme. Would you mind to revert the cygwin.sh changes? The following
patch should do it:
Index: util/cygwin.sh
===
RCS file: /home/cvs/cvsroot/src/openssl/util/cygwin.sh,v
retrieving revision 1.3
diff -u -p -r1.3 cygwin.sh
--- util/cygwin.sh 2003/01/09 16:15:46 1.3
+++ util/cygwin.sh 2003/01/13 14:35:19
@@ -114,13 +114,13 @@ strip usr/bin/*.exe usr/bin/*.dll
# Runtime package
find etc usr/bin usr/doc usr/ssl/certs usr/ssl/man/man[157] usr/ssl/misc \
usr/ssl/openssl.cnf usr/ssl/private -empty -o \! -type d |
-tar cjfT openssl2-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl-${VERSION}-${SUBVERSION}.tar.bz2 -
# Development package
find usr/include usr/lib usr/ssl/man/man3 -empty -o \! -type d |
-tar cjfT openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
-ls -l openssl2-${VERSION}-${SUBVERSION}.tar.bz2
-ls -l openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2
cleanup
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
In message [EMAIL PROTECTED] on Mon, 13 Jan 2003 15:36:40 +0100, Corinna Vinschen [EMAIL PROTECTED] said: vinschen in the meantime I released Cygwin's openssl using the above vinschen packaging scheme. Would you mind to revert the cygwin.sh vinschen changes? The following patch should do it: Applied and committed. -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ Unsolicited commercial email is subject to an archival fee of $400. See http://www.stacken.kth.se/~levitte/mail/ for more info. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
This is a preliminary patch and I need to think it through before I
commit it. Maybe we should solve it in some other way (like with ELF).
Any DJGPP out there who care to verify if this doesn't break DJGPP?
I tried this patch on DJGPP both as normally compiled and also using
the asm modules (put ${x86_out_asm} in the DJGPP config-string
^^^ Oh! I missed that. I mean the fact that they are not
actually engaged in the default configuration. Any particular reason
why?
No problems with compilation or testing.
Great! As for preliminarity of the patch. I've chosen to just promote
it to final and throw it in and not do something similar to ELF
solution. Basically because of lack of motivation:-) Cheers. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Sun, 12 Jan 2003, Andy Polyakov wrote:
I tried this patch on DJGPP both as normally compiled and also using
the asm modules (put ${x86_out_asm} in the DJGPP config-string
^^^ Oh! I missed that. I mean the fact that they are not
actually engaged in the default configuration. Any particular reason
why?
The only reason is to maintain 386 compatibility. The last time I
asked (I think it was about a year ago), there was a question as to
whether 386 incompatible instructions were used in the asm files, even
if 386 was specified in the Configure options. DJGPP programs should
be able to work on the 386 architecture. I don't have a 386 machine
to test with. I have no objection to using the asm files as long as
doing so doesn't break 386 compatibility. If the 386 compatibility
problem is real, perhaps instructions for changing the config-string
in Configure should be put in INSTALL.DJGPP, for those wishing to use
the asm files. I am not a programmer and don't know how to check for
assembler instructions incompatible with the 386 myself.
Doug
--
Doug Kaufman
Internet: [EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
I tried this patch on DJGPP both as normally compiled and also using
the asm modules (put ${x86_out_asm} in the DJGPP config-string
^^^ Oh! I missed that. I mean the fact that they are not
actually engaged in the default configuration. Any particular reason
why?
The only reason is to maintain 386 compatibility. The last time I
asked (I think it was about a year ago), there was a question as to
whether 386 incompatible instructions were used in the asm files, even
if 386 was specified in the Configure options.
If you './Configure ... DJGPP 386', then pure 386 asm code will be
generated. Well, it's all about single instruction, bswapl to be
specific... A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Sun, 12 Jan 2003, Andy Polyakov wrote:
I tried this patch on DJGPP both as normally compiled and also using
the asm modules (put ${x86_out_asm} in the DJGPP config-string
^^^ Oh! I missed that. I mean the fact that they are not
actually engaged in the default configuration. Any particular reason
why?
The only reason is to maintain 386 compatibility. The last time I
asked (I think it was about a year ago), there was a question as to
whether 386 incompatible instructions were used in the asm files, even
if 386 was specified in the Configure options.
If you './Configure ... DJGPP 386', then pure 386 asm code will be
generated. Well, it's all about single instruction, bswapl to be
specific... A.
In that case, it probably makes sense to make the asm code the
default in DJGPP also. This should just take a change in the DJGPP
config-string in Configure to put ${x86_out_asm} into the (currently
blank) next field after ${x86_gcc_opts}.
Doug
--
Doug Kaufman
Internet: [EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Thu, 9 Jan 2003, Andy Polyakov wrote:
I found the documentation for .def ... .endef, but it doesn't say a
thing about the values of .scl and .type. So I just copied from an .s
file generated by compiler. Verify the values with your people.
This is a preliminary patch and I need to think it through before I
commit it. Maybe we should solve it in some other way (like with ELF).
Any DJGPP out there who care to verify if this doesn't break DJGPP?
Oh! BTW, I probably have to object against calling the package openssl2,
openssl097 is probably more appropriate. A.
*** crypto/perlasm/x86asm.pl.orig Thu Jul 18 14:38:03 2002
--- crypto/perlasm/x86asm.plThu Jan 9 20:41:52 2003
I tried this patch on DJGPP both as normally compiled and also using
the asm modules (put ${x86_out_asm} in the DJGPP config-string in
Configure). No problems with compilation or testing.
Doug
--
Doug Kaufman
Internet: [EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Thu, Jan 09, 2003 at 10:35:16PM +0100, Corinna Vinschen wrote: The 2 is just sort of a counter which is needed to allow more than [...] Hi, I have chosen another packaging method: Version 0.9.6h will consist only of the needed DLLs to link applications build against it. The package will be called openssl096-0.9.6h-1.tar.bz2 The new 0.9.7 version will become the openssl package again, as the 0.9.6 version before. So the new packages are still just called openssl: openssl-0.9.7-1.tar.bz2 openssl-devel-0.9.7-1.tar.bz2 openssl-0.9.7-1-src.tar.bz2 That means, the patch to util/cygwin.sh can be reverted to create the normal openssh packages again instead of openssh2. Is that ok with you? Would you revert the cygwin.sh patch then? Thanks in advance, Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:[EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Tue, Dec 31, 2002 at 01:34:07AM +0100, Richard Levitte - VMS Whacker wrote:
-BEGIN PGP SIGNED MESSAGE-
OpenSSL version 0.9.7 released
===
Hi,
sorry for the late response but I didn't manage to test earlier :-(
I have two patches attached which are necessary to build 0.9.7 for
the Cygwin release. The Makefile.org patch is necessary to build
the Cygwin DLLs at all. It fixes a wrong sed expression. The patch
to util/cygwin.sh is required by the naming scheme used in the Cygwin
net release.
However, currently I'm unfortunately unable to release a Cygwin net
version of 0.9.7 due to a linker problem, which results in dropped
symbols in the link stub library. The most prominent dropped symbol
is RC4. Building OpenSSH with this libs results in ssh and sshd crashing
immediately :-((( I'm still in the process of trying to find out why
that happens.
Btw., does anybody have an idea where a symbol .RC4_end could come from?
Corinna
--- openssl-0.9.7.orig/Makefile.org 2002-12-30 00:03:16.0 +0100
+++ openssl-0.9.7/Makefile.org 2003-01-07 19:25:50.0 +0100
@@ -749,7 +749,7 @@ install: all install_docs
chmod 555
$(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new; \
mv -f
$(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i; \
else \
- c=`echo $$i | sed
's/^lib\(.*\)/cyg\1-$(SHLIB_VERSION_NUMBER)/'`; \
+ c=`echo $$i | sed
+'s/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`; \
cp $$c
$(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new; \
chmod 755
$(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new; \
mv -f
$(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new $(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c; \
--- openssl-0.9.7.orig/util/cygwin.sh 2002-11-14 13:39:51.0 +0100
+++ openssl-0.9.7/util/cygwin.sh2003-01-07 19:25:15.0 +0100
@@ -114,13 +114,13 @@ strip usr/bin/*.exe usr/bin/*.dll
# Runtime package
find etc usr/bin usr/doc usr/ssl/certs usr/ssl/man/man[157] usr/ssl/misc \
usr/ssl/openssl.cnf usr/ssl/private -empty -o \! -type d |
-tar cjfT openssl-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl2-${VERSION}-${SUBVERSION}.tar.bz2 -
# Development package
find usr/include usr/lib usr/ssl/man/man3 -empty -o \! -type d |
-tar cjfT openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
-ls -l openssl-${VERSION}-${SUBVERSION}.tar.bz2
-ls -l openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl2-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2
cleanup
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
In message [EMAIL PROTECTED] on Thu, 9 Jan 2003 17:05:12 +0100, Corinna Vinschen [EMAIL PROTECTED] said: vinschen Btw., does anybody have an idea where a symbol .RC4_end could come from? crypto/rc4/asm/rx86unix.cpp in my case (on Linux)... I've applied your patches, and will commit them promptly. Please check the next snapshot. -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ Unsolicited commercial email is subject to an archival fee of $400. See http://www.stacken.kth.se/~levitte/mail/ for more info. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Thu, Jan 09, 2003 at 05:10:55PM +0100, Richard Levitte - VMS Whacker wrote: In message [EMAIL PROTECTED] on Thu, 9 Jan 2003 17:05:12 +0100, Corinna Vinschen [EMAIL PROTECTED] said: vinschen Btw., does anybody have an idea where a symbol .RC4_end could come from? crypto/rc4/asm/rx86unix.cpp in my case (on Linux)... I've applied your patches, and will commit them promptly. Please check the next snapshot. Thanks, I just found out that the symbol comes from rx86unix.cpp in my case, too. What I don't understand is the following. crypto/rc4/Makefile.ssl contains the following: RC4_ENC=rc4_enc.o # or use #RC4_ENC=asm/rx86-elf.o #RC4_ENC=asm/rx86-out.o #RC4_ENC=asm/rx86-sol.o #RC4_ENC=asm/rx86bdsi.o Even though it's supposed to build rc4_enc.o to get the RC4 function(s), it builds asm/rx86-out.o instead. However, I found out, that the linker problem disappears if I build the libraries using rc4_enc.o instead of asm/rx86-out.o. Frankly, I have NO idea why! Until I found a solution for that linker problem (which is a linker bug, apparently) I'd like to build the Cygwin version using rc4_enc.o. How can I do that most cleanly? Thanks in advance, Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:[EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
However, currently I'm unfortunately unable to release a Cygwin net version of 0.9.7 due to a linker problem, which results in dropped symbols in the link stub library. The most prominent dropped symbol is RC4. Building OpenSSH with this libs results in ssh and sshd crashing immediately :-((( I'm still in the process of trying to find out why that happens. Btw., does anybody have an idea where a symbol .RC4_end could come from? I should have an idea... To start which I didn't expect to see .RC4_end symbol be visible at all. Assembler should have hidden it as names starting with . are supposed to be internal. I can double-check it later today. As for dropped RC4 symbol. I'm not really following... Did 'make test' pass? c=`echo $$i | sed 's/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`; ^ this of course works, but it probably should be \., not just dot:-) A. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Thu, Jan 09, 2003 at 05:34:39PM +0100, Andy Polyakov wrote: Btw., does anybody have an idea where a symbol .RC4_end could come from? I should have an idea... To start which I didn't expect to see .RC4_end symbol be visible at all. Assembler should have hidden it as names starting with . are supposed to be internal. I can double-check it later today. As for dropped RC4 symbol. I'm not really following... Did 'make test' pass? No. The problem is that when creating the link stub, the _RC4 symbol is treated as a data or bss symbol, not a text symbol. Linking against that link stub creates an illegal reference into the DLL == rc4test crashes. The same happens with _DES_ede3_cbc_encrypt and _DES_ncbc_encrypt, resulting in destest crashing. This all doesn't happen when linking against the static crypto lib, btw., it's justy a problem of the dynamic linking process. c=`echo $$i | sed 's/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`; ^ this of course works, but it probably should be \., not just dot:-) Oops, you're right. Thanks, Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:[EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
What I don't understand is the following. crypto/rc4/Makefile.ssl contains the following: RC4_ENC=rc4_enc.o # or use #RC4_ENC=asm/rx86-elf.o #RC4_ENC=asm/rx86-out.o #RC4_ENC=asm/rx86-sol.o #RC4_ENC=asm/rx86bdsi.o Even though it's supposed to build rc4_enc.o to get the RC4 function(s), it builds asm/rx86-out.o instead. RC4_ENC gets overriden from top Makefile. As for .*_end symbols. Apparently there're more... Any particular reason why are you complaining just about .RC4_end? Until I found a solution for that linker problem (which is a linker bug, apparently) I'd like to build the Cygwin version using rc4_enc.o. How can I do that most cleanly? By fixing rx86-out.o:-) A. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
In message [EMAIL PROTECTED] on Thu, 09 Jan 2003 17:34:39 +0100, Andy Polyakov [EMAIL PROTECTED] said: appro c=`echo $$i | sed 's/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`; appro ^ this of course works, but it probably appro should be \., not just dot:-) I saw it and fixed it before committing. -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ Unsolicited commercial email is subject to an archival fee of $400. See http://www.stacken.kth.se/~levitte/mail/ for more info. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
In message [EMAIL PROTECTED] on Thu, 9 Jan 2003 17:26:12 +0100, Corinna Vinschen [EMAIL PROTECTED] said: vinschen What I don't understand is the following. vinschen vinschen crypto/rc4/Makefile.ssl contains the following: vinschen vinschen RC4_ENC=rc4_enc.o vinschen # or use vinschen #RC4_ENC=asm/rx86-elf.o vinschen #RC4_ENC=asm/rx86-out.o vinschen #RC4_ENC=asm/rx86-sol.o vinschen #RC4_ENC=asm/rx86bdsi.o vinschen vinschen Even though it's supposed to build rc4_enc.o to get the RC4 vinschen function(s), it builds asm/rx86-out.o instead. What's given in crypto/rc4/Makefile.ssl is immaterial, since the correct values are passed on the command line by parent makes (see Makefile.ssl and crypto/Makefile.ssl). -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ Unsolicited commercial email is subject to an archival fee of $400. See http://www.stacken.kth.se/~levitte/mail/ for more info. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Thu, Jan 09, 2003 at 05:53:57PM +0100, Andy Polyakov wrote: As for .*_end symbols. Apparently there're more... Any particular reason why are you complaining just about .RC4_end? No. Just the one I found first due to the ssh crash. Until I found a solution for that linker problem (which is a linker bug, apparently) I'd like to build the Cygwin version using rc4_enc.o. How can I do that most cleanly? By fixing rx86-out.o:-) A. That doesn't help w/o details. I don't see anything wrong with that file. I have no idea why our linker treats RC4 from that file (and other functions from assembler files, apparently) as data. Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:[EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
As for .*_end symbols. Apparently there're more... Any particular reason why are you complaining just about .RC4_end? No. Just the one I found first due to the ssh crash. Until I found a solution for that linker problem (which is a linker bug, apparently) I'd like to build the Cygwin version using rc4_enc.o. How can I do that most cleanly? By fixing rx86-out.o:-) A. That doesn't help w/o details. I meant be patient:-) As for details, you should have provided more of them:-) At least that you've configured with shared flag and that 'make test' fails. In other words something we can *easily* reproduce. Cheers. A. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
Until I found a solution for that linker problem (which is a linker bug, apparently) I'd like to build the Cygwin version using rc4_enc.o. How can I do that most cleanly? By fixing rx86-out.o:-) A. Did it ever work? Assembler support in cygwin-shared build that is? BN stuff works, but I bet that's because routines from crypto/bn/asm/*.o are never called from application, but internally from within libcrypto.dll... A. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
Until I found a solution for that linker problem (which is a linker bug, apparently) I'd like to build the Cygwin version using rc4_enc.o. How can I do that most cleanly? By fixing rx86-out.o:-) A. Did it ever work? Assembler support in cygwin-shared build that is? BN stuff works, but I bet that's because routines from crypto/bn/asm/*.o are never called from application, but internally from within libcrypto.dll... A. OK, I've got test/rc4test.exe working, but I have to leave now... A. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Thu, Jan 09, 2003 at 06:32:05PM +0100, Andy Polyakov wrote: Until I found a solution for that linker problem (which is a linker bug, apparently) I'd like to build the Cygwin version using rc4_enc.o. How can I do that most cleanly? By fixing rx86-out.o:-) A. Did it ever work? Assembler support in cygwin-shared build that is? BN I can't tell. I never saw that problem before and in 0.9.6h all tests pass. Sorry, Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:[EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
And I don't think it's openssl's fault.
Yes, it apparently is... Compile foo(){} with cc -S and note that
compiler add some .def ... .endef line, but not perlasm thing which is
reponsible for assembler code generation.
I'm going
to ask some linker experts...
Ask about this .def ... .endef line. Any documentation available
on-line?
Did it ever work? Assembler support in cygwin-shared build that is? BN
I can't tell. I never saw that problem before and in 0.9.6h all tests
pass.
0.9.6h doesn't provide assembler support for Cygwin. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
And I don't think it's openssl's fault. Yes, it apparently is... Verify that the attached patch solves the problem. I'm going to ask some linker experts... Ask about this .def ... .endef line. Any documentation available on-line? I found the documentation for .def ... .endef, but it doesn't say a thing about the values of .scl and .type. So I just copied from an .s file generated by compiler. Verify the values with your people. This is a preliminary patch and I need to think it through before I commit it. Maybe we should solve it in some other way (like with ELF). Any DJGPP out there who care to verify if this doesn't break DJGPP? Oh! BTW, I probably have to object against calling the package openssl2, openssl097 is probably more appropriate. A. *** crypto/perlasm/x86asm.pl.orig Thu Jul 18 14:38:03 2002 --- crypto/perlasm/x86asm.plThu Jan 9 20:41:52 2003 *** *** 91,97 #undef SIZE #undef TYPE #define SIZE(a,b) ! #define TYPE(a,b) #endif /* __CYGWIN || __DJGPP */ #endif --- 91,97 #undef SIZE #undef TYPE #define SIZE(a,b) ! #define TYPE(a,b) .def a; .scl 2; .type 32; .endef #endif /* __CYGWIN || __DJGPP */ #endif __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.7 released
On Mon, Dec 30, 2002 at 10:45:30PM -0800, Kris Kennaway wrote:
On Tue, Dec 31, 2002 at 01:34:07AM +0100, Richard Levitte - VMS Whacker wrote:
o Support for new platforms: Windows CE, Tandem OSS, A/UX, AIX 64-bit,
Linux x86_64, Linux 64-bit on Sparc v9
OpenSSL does not compile out of the box on FreeBSD/SPARC (see
attached) - it tries to use the x86 FreeBSD-elf target. The
linux/sparc configuration is probably a base for fixing this.
Kris
This patch appears to fix it (I stole the OpenBSD-sparc64 config
target). OpenSSL builds and passes 'make test'.
Kris
--- config.orig Fri Dec 6 08:45:11 2002
+++ config Mon Dec 30 23:24:03 2002
@@ -206,6 +206,7 @@
Pentium\ II*) MACH=i686 ;;
Pentium*) MACH=i586 ;;
Alpha* ) MACH=alpha;;
+ *Sparc* ) MACH=sparc64 ;;
* ) MACH=$MACHINE ;;
esac
case ${MACH} in
@@ -640,6 +641,7 @@
*86*-*-solaris2) OUT=solaris-x86-$CC ;;
*-*-sunos4) OUT=sunos-$CC ;;
alpha*-*-freebsd*) OUT=FreeBSD-alpha ;;
+ sparc64-*-freebsd*) OUT=FreeBSD-sparc64 ;;
*-freebsd[3-9]*) OUT=FreeBSD-elf ;;
*-freebsd[1-2]*) OUT=FreeBSD ;;
*86*-*-netbsd) OUT=NetBSD-x86 ;;
--- Configure.orig Fri Dec 27 17:35:11 2002
+++ Configure Mon Dec 30 23:24:03 2002
@@ -396,6 +396,7 @@
NetBSD-m68, gcc:-DTERMIOS -O3 -fomit-frame-pointer -Wall
-DB_ENDIAN::(unknown):::BN_LLONG MD2_CHAR RC4_INDEX
DES_UNROLL::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
NetBSD-x86, gcc:-DTERMIOS -O3 -fomit-frame-pointer -m486
-Wall::(unknown):::BN_LLONG ${x86_gcc_des}
${x86_gcc_opts}::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
FreeBSD-elf, gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486
-Wall::-pthread -D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE:::BN_LLONG ${x86_gcc_des}
${x86_gcc_opts}:${x86_elf_asm}:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
+FreeBSD-sparc64,gcc:-DB_ENDIAN -DTERMIOS -O3
+-fomit-frame-pointer::(unknown):::SIXTY_FOUR_BIT_LONG DES_INT DES_PTR DES_RISC2
+BF_PTR::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
FreeBSD, gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486
-Wall::(unknown):::BN_LLONG ${x86_gcc_des} ${x86_gcc_opts}:${x86_out_asm},
bsdi-gcc, gcc:-O3 -ffast-math -DL_ENDIAN -DPERL5 -m486::(unknown):::RSA_LLONG
${x86_gcc_des} ${x86_gcc_opts}:${x86_bsdi_asm},
bsdi-elf-gcc, gcc:-DPERL5 -DL_ENDIAN -fomit-frame-pointer -O3 -m486
-Wall::(unknown)::-ldl:BN_LLONG ${x86_gcc_des}
${x86_gcc_opts}:${x86_elf_asm}:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
msg14674/pgp0.pgp
Description: PGP signature
