On Tue, Jul 24, 2018 at 08:34:28PM +0200, Kurt Roeckx wrote:
> On Tue, Jul 24, 2018 at 07:54:58PM +0200, Richard Levitte wrote:
> > ...
> > go test: FAILED (ServerNameExtensionServer-TLS1)
> > go test: unexpected failure: local error 'read tcp4
> > 127.0.0.1:41729->127.0.0.1:60574: rea
In message <84e6620a-e6bc-4f6e-a282-b46841b6d...@akamai.com> on Tue, 24 Jul
2018 18:05:35 +, "Salz, Rich" said:
rsalz> sudo cpan Carp::Always
rsalz>
rsalz> I did this. Same results for config and the PERLOPT setting.
For everyone's information, the breakage was really just rogue
On Tue, Jul 24, 2018 at 07:54:58PM +0200, Richard Levitte wrote:
> ...
> go test: FAILED (ServerNameExtensionServer-TLS1)
> go test: unexpected failure: local error 'read tcp4
> 127.0.0.1:41729->127.0.0.1:60574: read: connection reset by peer', child
> error 'signal: segmentation faul
sudo cpan Carp::Always
I did this. Same results for config and the PERLOPT setting.
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project
In message on Tue, 24 Jul
2018 17:50:50 +, "Salz, Rich" said:
rsalz>
rsalz>
rsalz> On 7/24/18, 1:42 PM, "Richard Levitte" wrote:
rsalz>
rsalz> Would you mind installing it? The package is called
rsalz> libcarp-always-perl on Debian and derivates, and if my RPM search fu
rsalz>
The master branch doesn't seem to be doing too well currently:
https://travis-ci.org/openssl/openssl/branches
The issue appears to be with the BoringSSL tests:
https://travis-ci.org/openssl/openssl/jobs/407676514
I see segfaults:
...
go test: FAILED (ServerNameExtensionServer-TLS1)
On 7/24/18, 1:42 PM, "Richard Levitte" wrote:
Would you mind installing it? The package is called
libcarp-always-perl on Debian and derivates, and if my RPM search fu
isn't entirely off, the corresponding RPM package is perl-Carp-Always
Or install with cpan...
Okay. Doe
Would you mind installing it? The package is called
libcarp-always-perl on Debian and derivates, and if my RPM search fu
isn't entirely off, the corresponding RPM package is perl-Carp-Always
Or install with cpan...
In message on Tue, 24 Jul
2018 17:36:49 +, "Salz, Rich" said:
rsalz> ; en
; env | grep PERL
; PERL5OPT=-MCarp::Always ./config
Operating system: x86_64-whatever-linux2
Can't locate Carp/Always.pm in @INC (you may need to install the Carp::Always
module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2
/usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /us
I can't reproduce, but looking into using Carp::Always uncovered a
couple of bugs, which I'm submitting a PR for. When that is merged,
you should be able to do this, and get a stack trace every time the
death handler is called:
PERL5OPT=-MCarp::Always ./config
BTW, would you be so kind and c
; g status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
; g pull
Current branch master is up to date.
;
; ./config
Operating system: x86_64-whatever-linux2
Configuring OpenSSL version 1.1.1-pre9-dev (0x10101009L) for linux-x86_64
Using
In message <20180724122839.ga2...@roeckx.be> on Tue, 24 Jul 2018 14:28:40
+0200, Kurt Roeckx said:
kurt> On Tue, Jul 24, 2018 at 02:08:46PM +0200, Richard Levitte wrote:
kurt> >
kurt> > The original intention (way back, I think we're even talking SSLeay
kurt> > time here, but at the very least
On Tue, Jul 24, 2018 at 02:28:40PM +0200, Kurt Roeckx wrote:
> On Tue, Jul 24, 2018 at 02:08:46PM +0200, Richard Levitte wrote:
> >
> > The original intention (way back, I think we're even talking SSLeay
> > time here, but at the very least pre-1.0.0 time) was to make a tarball
> > that can be bui
On Tue, Jul 24, 2018 at 02:08:46PM +0200, Richard Levitte wrote:
>
> The original intention (way back, I think we're even talking SSLeay
> time here, but at the very least pre-1.0.0 time) was to make a tarball
> that can be built directly with just a 'make' on any Unix box and
> without requiring
This is a question that's been asked before, and that has popped up
again in https://github.com/openssl/openssl/issues/6765
Our current mechanism for creating tarballs for a new OpenSSL release
is to run 'make dist' in any given build tree... it's a bit clumsy,
as it needs a wasted configuration
15 matches
Mail list logo
