On Fri, 2014 Sep 19 23:54+0200, Andy Polyakov via RT wrote:
> >
> > What system(s) are you testing on?
>
> We have discussed it earlier, 5.1. And was under impression that you
> target 5.1 too. You had older compiler, but system headers should have
> been same.
I have a 5.1 system too (though no a
On Fri, 2014 Sep 19 21:36+0200, Andy Polyakov via RT wrote:
>
> I suggest to resort for adding -DOPENSSL_USE_IPV6=0 at config time. I
> couldn't reproduce the problem on two different systems, so it's some
> problem with yours.
What system(s) are you testing on? Mine is "Digital UNIX V4.0G
(Rev.
Hi Andy,
On Fri, 2014 Sep 12 09:50+0200, Andy Polyakov via RT wrote:
> > http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=d1cf23ac86c05b22b8780e2c03b67230564d2d34
>
> With cross-reference to
> http://rt.openssl.org/Ticket/Display.html?id= can you confirm that
> preproc=/tmp/.$@
I am now building OpenSSL with non-default arguments, and am thus seeing
a new build error on Tru64 v5.1:
cc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include
-DOPENSSL_THREADS -pthread -DDSO_DLFCN -DHAVE_DLFCN_H -std1 -tune host
-fast -readonly_strings -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -
I'm reluctant to open an old issue, but Tru64 v5.1 is a corner case
unfortunately not covered by this fix.
(Andy: I am seeing this error now that I am building OpenSSL with
non-default build options.)
/usr/include/dlfcn.h on this system #defines RTLD_NEXT, but neither
Dl_info nor dladdr() are pre
On Tue, 2013 Nov 12 22:26+0100, Andy Polyakov via RT wrote:
> http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2df9ec01d563f9cc2deab07e8c3391059d476592
> http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5b63a392411822ef4252463cfb914a2ddeee06c6
> http://git.openssl.org/gitweb/?
On Sun, 2013 Nov 10 23:01+0100, Andy Polyakov via RT wrote:
>
> If 'perl | cc -E - > a.s' was used, then consequent 'cc -c a.s' was
> observing truncated file, as if buffer was not flushed in time.
Ah, strange. Maybe a bug in their early implementation of support for
preprocessing stdin.
(I think
On Sat, 2013 Nov 9 11:51+0100, Andy Polyakov via RT wrote:
>
> Or it's more likely that we're formulating it wrong. In sense that
> it's not OS, but *compiler* version that is crucial. It was tested
> with V6.5.
Fair enough; this 5.1 system has
$ cc -V
Compaq C V6.3-025 on Compaq Tru64
On Fri, 2013 Nov 8 23:05+0100, Andy Polyakov via RT wrote:
> >
> > * Tru64 cc(1) can't preprocess stdin; it needs a file
>
> You can't make such broad statement, as it was verified to work on
> 5.x.
Well, it doesn't work for 5.1:
$ uname -a
OSF1 darkstar V5.1 732 alpha
$ echo __osf__
I encountered a number of unusual (but mostly minor) errors in building
1.0.1e on Tru64 V4.0G, configuration tru64-alpha-cc. I've addressed the
majority of these in the 20131106 snapshot, and the changes are in the
attached patch. Here is a walk-through:
crypto/Makefile,
crypto/bn/Makefile,
crypto
10 matches
Mail list logo
