Hello,
Thank you for releasing 1.0.0l and 1.0.1f.
I tested them right away (that I haven't done for more than a year) found
that there are needed some changes in order to make the it work under
OpenVMS.
1. I have tested for the very first time with HP C V7.3-020 on OpenVMS IA64
V8.4 and
Hello,
I have tested OPENSSL-1.0.2-STABLE-SNAP-20140107 and found the following
problems that are mostly corrected (except the missing header file) with the
patch below:
1. missing header file unbound.h
#include unbound.h
.^
%CC-F-NOINCLFILEF, Cannot find file unbound.h specified in
-1.0.2-STABLE-SNAP-20140107 builds correctly and the
tests are passed as well on OpenVMS.
Thank you.
Regards,
Z
From: Zoltan Arpadffy [mailto:z...@polarhome.com]
Sent: den 7 januari 2014 23:11
To: 'openssl-dev@openssl.org'
Subject: [PATCH] changes required for OpenVMS in 1.0.2
Hello
Hello,
Sure, it is possible.
Thank you Stephen for reminding me for gnu diff from antinode.info
I am happy to use it.
Patches for 1.0.0l
SYSTEM@ia64$ mc dka0:utilgdiff.exe [.ssl]ssl-lib.com;1
[.ssl]ssl-lib.com;4
217c217
Hello,
On OpenVMS does not build that smooth as expected.
Please, find attached the patch needed to build on IA64 or Alpha platform.
NOTE: This patch contains a very dirty #define that should not be needed,
but for some reason in v3_scts.c BN_ULLONG is not defined.
Please, see the comments in
Hello,
I have tested to build on a HPUX box: HP-UX hpux-ia6 B.11.31 U ia64
0107668277 unlimited-user license
The hpux64-ia64-gcc build went perfect - all test passed.
From other side the default target hpux64-ia64-cc using Bundled CC does not
build.
Wrong options are configured.
cc
Thank you Steve,
I tested your last commit on OpenVMS - it works perfect now.
Regards,
Z
Quoting Dr. Stephen Henson st...@openssl.org:
On Mon, Feb 24, 2014, Zoltan Arpadffy wrote:
Hello,
On OpenVMS does not build that smooth as expected.
Please, find attached the patch needed to build
Hello,
Just for curiosity I tested on some less common Unix-es and architectures.
aix-gcc - OK
aix64-gcc - FAILED
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DAES_ASM -DVPAES_ASM -c -o
fips_ers.o fips_ers.c
ar -X64 r ../libcrypto.a cryptlib.o mem.o mem_dbg.o cversion.o ex_data.o
cpt_err.o ebcdic.o
Hello,
On my UnixWare it look even worse
bash-2.05a# uname -a
UnixWare unixware 5 7.1.4 i386 x86at SCO UNIX_SVR5
bash-2.05a# gcc --version
2.95.2
both unixware-7 and unixware-7-gcc target FAILED
gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H
Hello Andy,
I am sorry, but it did not help:
bash-2.05a# ./config -t
Operating system: i586-sco-unixware7
Configuring for unixware-7-gcc
/usr/bin/perl ./Configure unixware-7-gcc no-sse2
bash-2.05a# /usr/bin/perl ./Configure unixware-7-gcc no-sse2
Configuring for unixware-7-gcc
no-dane
Hello Andy,
you are right - in some cases I forgot to do make clean between two builds.
Now, I did a focused, thorough test based on
openssl-1.0.2-stable-SNAP-20140226
Here are the results:
*IRIX*
bash-2.05b$ uname -a
IRIX64 irix 6.5 07202013 IP35
bash-2.05b$ gcc --version
gcc (GCC) 3.3
Hello,
Quoting Zoltan Arpadffy z...@polarhome.com:
*Ultrix*
bash-2.05# uname -a
ULTRIX ultrix 4.5 0 VAX
bash-2.05# gcc --version
2.7.2
bash-2.05# what /bin/cc
/bin/cc:
crt0.c 9.1 ULTRIX 4/26/94
cc.c9.1 (ULTRIX)4/27/94
printf.c9.1
Hello,
I have tested today OPENSSL-1.0.2-STABLE-SNAP-20140402 and find out
that it fails to build on OpenVMS.
The following patch is needed to make it work.
SYSTEM@ia64$ mc DKA0:[UTIL]gdiff -p [.crypto]crypto-lib.com;1
[.crypto]crypto-lib.com;2
*** [.crypto]crypto-lib.com;1 Tue Feb
Right approach Steven.
Mea culpa :(
I am terribly sorry proposing ignorance of MAYLOSEDATA3 while not testing on
older compilers.
Thank you.
Regards,
Z
-Original Message-
From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org]
On Behalf Of Steven M. Schweda
Sent:
Hi,
another area where OpenSSL needs competent contibution is testing.
Build OpenSSL on as many different platforms, architectures using as
many different compilers as possible and turn off/on different
swithes, features and test if it works.
In the beginning the UC tests would be enough,
Hi,
the 1.0.0m fails to build on OpenVMS Alpha architecture.
OPENSSL_assert(s-s3-wnum INT_MAX);
^
%CC-E-UNDECLARED, In this statement, INT_MAX is not declared.
at line number 586 in file DKA300:[WORK.OPENSSL-100M.SSL]S3_PKT.C;1
On IA64 and VAX it builds well.
I'll return
:42, Zoltan Arpadffy z...@polarhome.com wrote:
Hi,
the 1.0.0m fails to build on OpenVMS Alpha architecture.
OPENSSL_assert(s-s3-wnum INT_MAX); ^
%CC-E-UNDECLARED, In this statement, INT_MAX is not declared.
at line number 586 in file DKA300:[WORK.OPENSSL-100M.SSL]S3_PKT.C;1
-net.net
$!
$! Changes by Richard Levitte rich...@levitte.org
+ $! Zoltan Arpadffy arpad...@polarhome.com
$!
$! This command files compiles and creates all the various different
$! test programs for the different types of encryption for OpenSSL.
*** $ TEST_FILES
/decc_alpha_help_4.html#Ref504
In message 002401cf52e5$5791b8f0$06b52ad0$@com on Tue, 8 Apr 2014
06:45:18 +0200, Zoltan Arpadffy z...@polarhome.com said:
zoli Right approach Steven.
zoli
zoli Mea culpa :(
zoli I am terribly sorry proposing ignorance of MAYLOSEDATA3 while
not testing on
zoli older
Hi Richard,
It seems that duplicating the check on the existence of MAYLOSEDATA3 in
the other building .com files would be the way to go.
I totally agree.
I would even suggest to merge back the changes to the 1.0.1 and even to the
1.0.0 branch too.
Thanks,
Z
Hi,
I see that Rich is doing a fantastic job by cleaning up the backlog...
I absolutely agree that very old releases cannot be supported, but what about
the platforms?
I thought until now, that as long there are developers who are willing to
develop for a certain platform and there is some
Hi,
I absolutely agree, that other less popular platforms need support.
Unfortunately, reading the conversation in the last few days, I got a
feeling that the OpenSSL core development is not willing to support
those platforms in the main line, but will come up with a separate
branch or
You are most welcome.
This is the main purpose of polarhome.
I have been working few days with that setup and I see already that it
will not be as smooth as somebody would guess, because java, git etc
are not available, or supported on every system.
I have sent a preview to Tim, but when
Hi,
I was working a lot with Netware some 10-15 years ago.
I wonder if you have some recent install media with ev. licence to
donate to polarhome.com
I am building up a jenkins farm with polarhome servers that would
build OpenSSL, Vim and other opensource projects and follow up CI.
That
and Zoltan Arpadffy, as they have been fairly
vocal as well as deservingly critical, and thereby hopefully interested, but
others are free to join as well)
Cheers,
Richard
--
Richard Levitte rich...@levitte.org
http
Hi,
Unfortunately, Matt's latest fix around CFLAGS define ( for making the build
work on Windows) does not help on OpenVMS.
The following additional patch is needed.
SYSTEM@ia64$ mc DKA0:[UTIL]gdiff.exe -p []makevms.com;1 []makevms.com;2
*** []makevms.com;1 Wed Jan 7 16:00:30 2015
Hi,
during installation of 1.0.0 branch on OpenVMS the following error appears.
%COPY-E-OPENIN, error opening
IA64$DKA0:[WORK.OPENSSL-100-STABLE-SNAP-20150109.CRYPTO.SRP]SRP.H; as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
The solution is to apply the following
Hi,
I am sorry for the late reply, but I was very busy nowadays with other issues.
Were there any errors during the build?
On polarhome's IA64 (running as SYSTEM user) is not possible to
reproduce the error:
SYSTEM@ia64$ .testtests.com test_ssl
%DCL-W-NOCOMD, no command on line - reenter with
Hi,
I am sorry, but because of the relocation of the header files the 1.1.0 does
not build on OpenVMS.
Please, allow some time to fix the OpenVMS build scripts.
Thank you.
Regards,
Z
-Original Message-
From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of
OpenSSL
;:
The building scripts are not at all updated, it's beyond repair. I'm
(slowly) working on a new solution that doesn't require the separate
update hell...
Cheers
Richard
Zoltan Arpadffy <z...@polarhome.com> skrev: (21 december 2015 20:36:13 CET)
Hi,
I am sorry, but because of the relocati
Hi,
zoli> > (unfortunately, "cpan install Text::Template" doesn't work because
zoli> > there's a lack of action lines in the test: target it its Makefile,
zoli> > and mms isn't too happy about that...)
That's tough, unfortunately... I've only access to a V8.4 cluster
(Alpha and IA64), so I
Hi,
zoli> May I ask you, if the new build will cover the long names issue (
zoli> symhacks.h ) too?
It's been pointed out to me by the vms-ports folks that it should be
possible to solve using the compiler's "#pragma names shortened"
rather than maintaining symhacks... Then, it's just a
Hi,
Unfortunately, the Matt's latest fix around CFLAGS define ( for making the
build work on Windows) does not help on OpenVMS.
The following path is needed.
SYSTEM@ia64$ mc DKA0:[UTIL]gdiff.exe -p []makevms.com;1 []makevms.com;2
*** []makevms.com;1 Wed Jan 7 16:00:30 2015
---
33 matches
Mail list logo
