Re: OpenSSL 1.0.0 beta3 release v. VMS
|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
 |
Re: OpenSSL 1.0.0 beta3 release v. VMS
by Steven M. Schweda-2
::
Rate this Message:
From: "Arpadffy Zoltan" <Zoltan.Arpadffy@...>
> As you probably know VMS has a different DIFF output than UNIX diff and > is not able to produce patch output. > > Please advice, how can I share my changes. > > May I submit a standard VMS diff output here? You might try GNU "diff" for VMS: http://antinode.info/dec/sw/diffutils.html No guarantees, but it has worked for me. Wake me (directly) if you have any questions on it or problems with it. ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-info 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... |
|
|
[PATCH] OpenSSL 1.0.0 beta3 release v. VMS
by Arpadffy Zoltan
::
Rate this Message:
Mandatory information:
Request type: PATCH OS and arch: OpenVMS ALPHA, IA64 OpenSSL version: 1.0.0 beta 3 Hello, This patch corrects build on OpenVMS systems. I have tested on ALPHA and IA64 platform with DECC. As VMS does not have a make clean function yet, it was hard to separate the really modified files from the copied (poor symlink imitation on VMS) etc. I hope that I have not missed anything. The ALL target has built successfully, tests passed (check the TODO) and installed the libraries, executables and header files. TODO: - test on VAX - test with other compilers than DECC - add support for building 32 and 64 bits libraries - testca and testtsa fails (can not find .rnd file) - test if everything is there - compare more in detail unix makefiles with VMS OPTIONAL TODO - in order to make life more compatible we could use the same logicals like HP's SSL product - I mean SSL$ROOT instead of SSLROOT Have a nice weekend :) Best regards, Zoltan Arpadffy -----Original Message----- From: Steven M. Schweda [mailto:sms@...] Sent: den 12 augusti 2009 21:05 To: openssl-dev@... Subject: Re: OpenSSL 1.0.0 beta3 release v. VMS From: "Arpadffy Zoltan" <Zoltan.Arpadffy@...> > As you probably know VMS has a different DIFF output than UNIX diff and > is not able to produce patch output. > > Please advice, how can I share my changes. > > May I submit a standard VMS diff output here? You might try GNU "diff" for VMS: http://antinode.info/dec/sw/diffutils.html No guarantees, but it has worked for me. Wake me (directly) if you have any questions on it or problems with it. ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-info 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 |
|
|
|
|
|
RE: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS
by Arpadffy Zoltan
::
Rate this Message:
Hello,
> Copied files? What's copied? In makevms.com ALL target will do a SOFTLINKS by the way, that will do a lot of coping around. I agree that with the right /INCLUDE parameter it would be more appropriate to build. I'll add this as well to my TODO list. >> - test with other compilers than DECC > Who uses anything else? The build scripts are prepared for VAXC and for GCC as well. I share your opinion that these compilers are not used that often nowadays... but on old vaxes VAXC still rules and GCC might get a wing in the future. It is worth testing at all, unfortunately I do not have environment for that. >> OPTIONAL TODO >> - in order to make life more compatible we could use the same logicals >> like HP's SSL product - I mean SSL$ROOT instead of SSLROOT >If there _is_ a good reason to make a change like this, please explain why In the past almost 10 years nobody used any other SSL on OpenVMS but HP's. I know that it is utopist thought - but I would prefer to have one SSL library on OpenVMS - even better it that would be supported by HP itself. It is rather easy to make few steps towards HP's SSL build that might motivate and encourage HP to send back their changes to the openssl community. Like this the whole OpenVMS community would benefit... as well as HP's supported SSL product build would be trivial and reduce to regression tests and repackaging. I am an optimist and unitarist who still believe in tolerance and free will's good choices. Regards, Z -----Original Message----- From: Steven M. Schweda [mailto:sms@...] Sent: den 15 augusti 2009 18:39 To: openssl-dev@... Subject: Re: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS From: "Arpadffy Zoltan" <Zoltan.Arpadffy@...> > This patch corrects build on OpenVMS systems. I haven't looked at it yet, but ... > As VMS does not have a make clean function yet, it was hard to separate > the really modified files from the copied (poor symlink imitation on > VMS) etc. Copied files? What's copied? I thought that I had eliminated all the file copying (and the need for any symlinks). > TODO: > [...] > - test with other compilers than DECC Who uses anything else? > OPTIONAL TODO > - in order to make life more compatible we could use the same logicals > like HP's SSL product - I mean SSL$ROOT instead of SSLROOT I changed the library names from xxx to SSL_xxx to look more like HP's SSL$xxx (and so I could find them), but I don't see a good reason to go further than that. I believe that many people and procedures use these SSL* logical names to determine which SSL package is being used. Making everything look exactly the same would seem likely to cause more trouble than leaving them different. If there _is_ a good reason to make a change like this, please explain why, how, and so on, and why it wouldn't break a lot of existing stuff. ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-info 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... |
|
|
|
|
|
|
|
|
|
|
|
Re: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS
by Richard Levitte - VMS Whacker
::
Rate this Message:
(resend)
In message <09081709341183_202004B7@...> on Mon, 17 Aug 2009 09:34:11 -0500 (CDT), sms@... (Steven M. Schweda) said: sms> From: "Arpadffy Zoltan" <Zoltan.Arpadffy@...> sms> sms> > As VMS does not have a make clean function yet, [...] sms> sms> When _all_ the product files get put into architecture-specific sms> directories, then cleaning gets easy. Agreed, but except for cleaning purposes, is there a reason to put architecture-independent files in architecture-specific directories? sms> I haven't done anything with the new (1.0.0 beta X) stuff sms> because it wasn't not clear that anyone was looking at the sms> changes I made to the old stuff. It's still not clear. I've looked, as I've said before. I've also applied the functional bits. Not the cosmetic bits, not the non-copying bits, as they really should make no difference, or? Also, the SSLfoo to SSL_foo logical name conversion... hmm, did I apply that? If I did, it should be reverted, at least in the 0.9.8 series, as such a change will only confuse the users... sms> I have a VAX with V5.5-2 and VAX C on it, but I'd be amazed if sms> this code could be built using VAX C. The only GNU C I have is sms> also on that VAX, and it's even older than the VAX C. I assumed sms> that the non-DEC-C code was all fossils, but it seemed harmless sms> to leave it in. The builds haven't worked on VAX with _any_ sms> compiler for so long that it's hard to imagine that anyone is sms> still using VAX C or GNU C there. I haven't had a VAX account for a long time... someone give me one and I'll play... sms> From: Richard Levitte [mailto:richard@...] sms> sms> > I've looked through it, and applied almost all of it. [...] sms> sms> If more than one person will be making big changes to these sms> builders, then it might make some sense to discuss the changes sms> before applying all of anything to the code. If those who do commit to the repository, I believe I'm the only one dealing with the VMS parts of the kit... Andy might play, but his focus is on other things, I think... sms> I had what I thought was a whole, working 0.9.8k kit, where sms> "working" means that the builds went through on VAX, Alpha, and sms> IA64. Some of those changes seem to have made it to 1.0.0 beta sms> 3, but not all, and I don't know why. I've asked, but I hear sms> nothing. I can't see a good reason to make the same changes over sms> and over again if they do not get adopted, and no one says why sms> they do not get adopted. What am I missing? Is there some plan sms> here? The plan I worked with (and thought I said) was to take the functional bits first, have them work, and take the cosmetics later... I had to do quite a lot of reading through your patches to extract what I judged to be functional. I may have missed some bits. Cheers, Richard -- Richard Levitte richard@... http://richard.levitte.org/ "Life is a tremendous celebration - and I'm invited!" -- from a friend's blog, translated from Swedish ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... |
|
|
RE: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS
by Arpadffy Zoltan
::
Rate this Message:
Hello,
> I haven't had a VAX account for a long time... someone give me one and I'll play... You can create your own account at http://www.polarhome.com/service/shell/ ... and just drop me a mail informing me what is you username. Regards, Z ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... |
|
|
|
|
|
RE: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS
by Arpadffy Zoltan
::
Rate this Message:
Hello Richard, >If those who do commit to the repository, I believe I'm the only one >dealing with the VMS parts of the kit... I tested OPENSSL-VMS_64BIT-SNAP-20090821 as I was expecting that my changes would be there. I was wrong :( I wonder, where do you apply the patches and patch suggestions? Is there any source snapshot that is possible to test? Thank you. Have a nice weekend. Regards, Z ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... |
|
|
Re: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS
by Richard Levitte - VMS Whacker
::
Rate this Message:
In message <839C820B5C926B4B89713B3A6ED68D2AAE49C2@...> on Fri, 21 Aug 2009 17:36:08 +0200, "Arpadffy Zoltan" <Zoltan.Arpadffy@...> said:
Zoltan.Arpadffy> Zoltan.Arpadffy> Zoltan.Arpadffy> Hello Richard, Zoltan.Arpadffy> Zoltan.Arpadffy> >If those who do commit to the repository, I believe I'm the only one Zoltan.Arpadffy> >dealing with the VMS parts of the kit... Zoltan.Arpadffy> Zoltan.Arpadffy> I tested OPENSSL-VMS_64BIT-SNAP-20090821 as I was expecting that my Zoltan.Arpadffy> changes would be there. Zoltan.Arpadffy> I was wrong :( Yes. I'm committing your changes (as well as sms') directly to the 1.0.0 branch as well as the 0.9.8 branch. Cheers, Richard -- Richard Levitte richard@... http://richard.levitte.org/ "Life is a tremendous celebration - and I'm invited!" -- from a friend's blog, translated from Swedish ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... |
|
|
RE: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS
by Arpadffy Zoltan
::
Rate this Message:
Hello,
It has passed few months and it is getting closer to the official release of v1.0.0. I have recently checked out the source from the CVS and tested the VMS build and in order to finalize issues from my TODO lis: - add support for building 32 and 64 bits libraries - testca and testtsa fails (can not find .rnd file) Unfortunately, the build failed. Wonder: 1. is it right assumption that the last cvs checkout should contain all recent patches, changes for 1.0.0? 2. Have all VMS related changes that I have sent been merged into the code? (1.0.0beta3 builds nice with my patches on VMS) 3. How should we proceed? Should I send a new patch that corrects VMS build against latest code from the cvs? I would like to see openssl building correctly on OpenVMS before 1.0.0 is released. Hope that this is a common goal. Thank you in advance. Regards, Z -----Original Message----- From: Richard Levitte [mailto:richard@...] Sent: den 25 augusti 2009 10:09 To: openssl-dev@...; Arpadffy Zoltan Subject: Re: [PATCH] OpenSSL 1.0.0 beta3 release v. VMS In message <839C820B5C926B4B89713B3A6ED68D2AAE49C2@...> on Fri, 21 Aug 2009 17:36:08 +0200, "Arpadffy Zoltan" <Zoltan.Arpadffy@...> said: Zoltan.Arpadffy> Zoltan.Arpadffy> Zoltan.Arpadffy> Hello Richard, Zoltan.Arpadffy> Zoltan.Arpadffy> >If those who do commit to the repository, I believe I'm the only one Zoltan.Arpadffy> >dealing with the VMS parts of the kit... Zoltan.Arpadffy> Zoltan.Arpadffy> I tested OPENSSL-VMS_64BIT-SNAP-20090821 as I was expecting that my Zoltan.Arpadffy> changes would be there. Zoltan.Arpadffy> I was wrong :( Yes. I'm committing your changes (as well as sms') directly to the 1.0.0 branch as well as the 0.9.8 branch. Cheers, Richard -- Richard Levitte richard@... http://richard.levitte.org/ "Life is a tremendous celebration - and I'm invited!" -- from a friend's blog, translated from Swedish ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@... Automated List Manager majordomo@... |
openssl-1.0.0.beta3-vms.zip (7K) 
| Free embeddable forum powered by Nabble | Forum Help |
