Hi,
We (ATOS BullFreeware project) are building and delivering OpenSSL on AIX.
However, there are different providers of OpenSSL on AIX (IBM AIX project,
Perzl, Bull Freeware, IBM AIX Toolbox), and we have some compatibility issues
when mixing RPMs depending on OpenSSL and built with different
Reading the 1.0.2j CHANGES file, it appears that 1.0.2 was built from 1.0.1l.
And there are 1124 of description of the changes for 1.0.2 and about 500 lines
of changes from 1.0.1l to 1.0.1u .
And my knowledge of OpenSSL is VERY VERY small.
Looking at 1.0.1l, out of bug fixes, I've found some
Hi,
We (BullFreeware project: http://www.bullfreeware.com/) port OpenSSL on AIX,
since ages.
Since BullFreeware is not a distro (we do not deliver packages built
all-together, rather we deliver RPM packages than may stay un-updated during
years), we maintain a compatibility with older
Hi,
Looking at crypto/opensslv.h of version 1.0.2f, it says:
# define SHLIB_VERSION_NUMBER "1.0.0"
Shouldn't it be 1.0.2 ??
On AIX, we provide previous versions (32 & 64 bots) of libssl.so and
libcrypto.so , for compatibility, like:
libssl.so.0.9.7
libssl.so.0.9.8
libssl.so.1.0.0
and,
Thanks.
I was asking because, when looking at the traces of the build (on AIX and
Intel), I see several things like:
if [ -n "" ]; then \
(cd ..; gmake libcrypto.so.1.0.0); \
fi
where 1.0.0 comes from SHLIB_VERSION_NUMBER defined in crypto/opensslv.h .
And it looked wrong to me. At
Hi,
Runing one test can be done with GCC and the following process:
$ make clean
$ export CC="gcc -fprofile-arcs -ftest-coverage"; ./config enable-unit-test
$ make depend
$ make
$ make TESTS="test_cms" test
$ make TESTS=test_heartbeat test
However, on AIX, I'm using xlC, which does not
Hi,
I'm trying to build last versions of OpenSSL on AIX 6.1, as RPMs with .spec
files.
With versions 1.0.1p and 1.0.2d , on same machine, my .spec file works
perfectly.
Now, with versions 1.0.1r and 1.0.2f, my .spec file (changing 1.0.2d to 1.0.2f)
breaks as:
make[2]: Entering directory
