Re: 2.4.18 backporting

2015-11-18 Thread Jim Jagielski
t;>> ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', >>>>>>>> lseeksize=8 >>>>>>>> alignbytes=8, prototype=define >>>>>>>> Linker and Libraries: >>>>>&g

Re: 2.4.18 backporting

2015-11-18 Thread Stefan Eissing
, >>>>>>> lseeksize=8 >>>>>>> alignbytes=8, prototype=define >>>>>>> Linker and Libraries: >>>>>>> ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc', ldflags =' -fstack-protector >>>>>>>

Re: 2.4.18 backporting

2015-11-17 Thread Stefan Eissing
gt;>>>> lseeksize=8 >>>>>>> alignbytes=8, prototype=define >>>>>>> Linker and Libraries: >>>>>>> ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc', ldflags =' -fstack-protector >>>>>>> -L

Re: 2.4.18 backporting

2015-11-17 Thread Jim Jagielski
loper/Toolchains/XcodeDefault.xctoolchain/usr/lib >>>>>> /usr/lib /opt/local/lib >>>>>> libs=-lgdbm -ldbm -ldl -lm -lutil -lc >>>>>> perllibs=-ldl -lm -lutil -lc >>>>>> libc=, so=dylib, useshrplib=true, libperl=libperl.dyli

Re: 2.4.18 backporting

2015-11-17 Thread Stefan Eissing
gt;> gnulibc_version='' >>>>> Dynamic Linking: >>>>> dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' ' >>>>> cccdlflags=' ', lddlflags=' -bundle -undefined dynamic_lookup >>>>> -L/usr/local/lib

Re: 2.4.18 backporting

2015-11-17 Thread Jim Jagielski
t;>> >>>>> On Nov 17, 2015, at 9:59 AM, Stefan Eissing >>>>> wrote: >>>>> >>>>> Hmm, what perl version is that? Works on my OS X (El 10.11) with perl -v: >>>>> >>>>> This is perl 5, version 18, subversion 2 (v5.18.2)

Re: 2.4.18 backporting

2015-11-17 Thread Stefan Eissing
built for >>>> darwin-thread-multi-2level >>>> (with 2 registered patches, see perl -V for more detail) >>>> >>>> //Stefan >>>> >>>>> Am 17.11.2015 um 15:44 schrieb Jim Jagielski : >>>>> >>>>>

Re: 2.4.18 backporting

2015-11-17 Thread Jim Jagielski
Jagielski : >>>> >>>> Doing a quick tst I get: >>>> >>>> t/modules/http2.t .. push on reference is experimental at >>>> t/modules/http2.t line 319. >>>> Dubious, test returned 255 (wstat 65280, 0xff00) >>>>

Re: 2.4.18 backporting

2015-11-17 Thread Stefan Eissing
-- >>> t/modules/http2.t (Wstat: 65280 Tests: 0 Failed: 0) >>> Non-zero exit status: 255 >>> Parse errors: No plan found in TAP output >>> Files=1, Tests=0, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.31 cusr 0.06 >>> csys = 0.40 CPU)

Re: 2.4.18 backporting

2015-11-17 Thread Jim Jagielski
using perl 5.18 I get: t/modules/http2.t ... 1/51 # Failed test 34 in t/modules/http2.t at line 242 fail #4 # Failed test 50 in t/modules/http2.t at line 194 fail #6 # Failed test 51 in t/modules/http2.t at line 194 fail #7 # testing : content comparision # expected: ' # Hello Wor

Re: 2.4.18 backporting

2015-11-17 Thread Jim Jagielski
http2.t (Wstat: 65280 Tests: 0 Failed: 0) >> Non-zero exit status: 255 >> Parse errors: No plan found in TAP output >> Files=1, Tests=0, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.31 cusr 0.06 >> csys = 0.40 CPU) >> Result: FAIL >> Failed 1/1 test programs.

Re: 2.4.18 backporting

2015-11-17 Thread Stefan Eissing
s is on OSX > >> On Nov 17, 2015, at 8:12 AM, Jim Jagielski wrote: >> >> I will. >> >>> On Nov 17, 2015, at 7:47 AM, Stefan Eissing >>> wrote: >>> >>> For the 2.4.18 backporting, can I find people here willing to look at: >&g

Re: 2.4.18 backporting

2015-11-17 Thread Jim Jagielski
; > I will. > >> On Nov 17, 2015, at 7:47 AM, Stefan Eissing >> wrote: >> >> For the 2.4.18 backporting, can I find people here willing to look at: >> >> *) core/mod_ssl: >>- master conn_rec* addition to conn_rec >>- minor mmn bump

Re: 2.4.18 backporting

2015-11-17 Thread Jim Jagielski
I will. > On Nov 17, 2015, at 7:47 AM, Stefan Eissing > wrote: > > For the 2.4.18 backporting, can I find people here willing to look at: > > *) core/mod_ssl: > - master conn_rec* addition to conn_rec > - minor mmn bump > - improved ALPN and Upgrad

2.4.18 backporting

2015-11-17 Thread Stefan Eissing
For the 2.4.18 backporting, can I find people here willing to look at: *) core/mod_ssl: - master conn_rec* addition to conn_rec - minor mmn bump - improved ALPN and Upgrade handling - allowing requests for servers whose TLS configuration is compatible to the SNI