There are
In message <839c820b5c926b4b89713b3a6ed68d2a9aa...@sgstmail.scigames.at> on
Fri, 29 May 2009 15:55:59 +0200, "Arpadffy Zoltan"
<zoltan.arpad...@scientificgames.se> said:
Zoltan.Arpadffy> I have made an attempt to build 0.9.8k on OpenVMS -
Zoltan.Arpadffy> and this is a disaster :(
I hear you. The build procedure hasn't been updated much at all in
the last few years, and basically, that's my failure.
Zoltan.Arpadffy> This was the very first time that tried to build
Zoltan.Arpadffy> openssl on VMS from original openssl.org release and
Zoltan.Arpadffy> I find out that provided VMS build scripts are not up
Zoltan.Arpadffy> to date.
I did some updates after 0.9.8k that got it ro work again, as far as I
could build on Alpha (the only platgform I currently have available)
Zoltan.Arpadffy> I see also that there were still some efforts to
Zoltan.Arpadffy> update those scripts too as the source has
Zoltan.Arpadffy> evolved/developed but the scripts have not been
Zoltan.Arpadffy> tested and do not build the libraries and the
Zoltan.Arpadffy> executables correctly...
Please enlighten me as to what you mean with "correctly".
Zoltan.Arpadffy> moreover the VMS build supports just VAX and AXP
Zoltan.Arpadffy> architecture but not IA64.
That's true. There's an ongoing but slow effort to bring the scripts
up to date for IA64 as well right now.
Zoltan.Arpadffy> The following questions arise and I would like to
Zoltan.Arpadffy> discuss with somebody what the possibilities are and
Zoltan.Arpadffy> how to solve those issues.
Zoltan.Arpadffy>
Zoltan.Arpadffy> 1. I understand that the openssl license does not
Zoltan.Arpadffy> force HP to share, provide, publish and merge back
Zoltan.Arpadffy> the HP changes to the openssl.org source. I also
Zoltan.Arpadffy> understand that if HP would like to make sure that
Zoltan.Arpadffy> the next openssl.org release would be VMS compatible
Zoltan.Arpadffy> that HP would submit the changes... But the HP
Zoltan.Arpadffy> sources are public as well and the working solution
Zoltan.Arpadffy> is available for everybody. The question is: Is it
Zoltan.Arpadffy> legal to use HP's solution and merge into the openssl
Zoltan.Arpadffy> source?
That depends on the license HP's building solution is under.
Zoltan.Arpadffy> As I am personally very interested that openssl runs
Zoltan.Arpadffy> and builds correctly on OpenVMS, I am willing to
Zoltan.Arpadffy> contribute... just wonder why this is not done so
Zoltan.Arpadffy> far?
;-) well, only you can say why you haven't contributed so far ;-)
Zoltan.Arpadffy> With making a proper functional make/build scripts
Zoltan.Arpadffy> for VMS everybody would benefit.
"proper" is an opinion, and everybody will have one, me included. I'm
ready to listen, of course, provided I have the time to spend...
Zoltan.Arpadffy> Primarily we, OpenVMS users would benefit as well as
Zoltan.Arpadffy> HP who could skip the development and maintenance of
Zoltan.Arpadffy> its own SSL releases.
HP makes a product from OpenSSL, called HP SSL. HP will keep on
having their own development making that product, with their own
logical and library names. I don't think we should step there,
that'll only create confusion.
Cheers,
Richard
--
Richard Levitte rich...@levitte.org
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@openssl.org
Automated List Manager majord...@openssl.org
