[RELEASE CANDIDATE] mod_perl-1.31 RC3

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig00FAA693FCF6F851236E9308
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

The mod_perl 1.31 release candidate 3 "Works with Perl 5.10" is ready. It=
can be downloaded here:

http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc3.tar.gz

MD5: 979059e20febef686e7c2a4d55fe3683
SHA1: c747ef7d605694ca935795ea7793ea7c77dfa920

The summary of what has changed since 1.30 are (from Changes):

Fix static APACI build against newer apache-1.3.38+
[Gozer]

Fixed modules/regex.t test 4 on Win32
[Steve Hay]

Avoid possible segfault when PerlFreshRestart is On.
[Michael Rendell ]

Prevent segfault when running with perl >=3D 5.9.3
[Steve Hay]

Fix shared libary extensions on Win32 to be .dll not .so
[Nikolay Ananiev ]

Patch to mod_perl.dsp to remove /D _WINSOCK2API_ on Win32
for perl >=3D 5.8.6 [Steve Hay]

--=20
Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/ m/gozer\@(apache|cpan|ectoplasm)\.org/


--------------enig00FAA693FCF6F851236E9308
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHw9wByzKhB4jDpaURAsaIAJ9E3rKicpdWOCXM74u8x8YRchaBCACg xO0Q
+zw4/dnSJifbe/57vAE+BKA=
=bfcy
-----END PGP SIGNATURE-----

--------------enig00FAA693FCF6F851236E9308--

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC3

> The mod_perl 1.31 release candidate 3 "Works with Perl 5.10" is ready. It
> can be downloaded here:
>
> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc3.tar.gz

Works with 5.8.8 also, darwin 10.5, apache 1.3.41
Files=37, Tests=405, 5 wallclock secs ( 3.20 cusr + 0.60 csys = 3.80 CPU)

+1

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC3

win32 (xp sp2, vc6 - no SDK upgrade) - Apache 1.41 binary - ActivePerl
5.10 (build 1002)
FAIL

(sorry, folks)

Segfault at startup.

last line in mod_perl-land:
mod_perl.c : 704
status = perl_parse(perl, mod_perl_xs_init, argc, argv, NULL);

I can't download the AS perl source - it keeps stopping or hanging in
the middle, but that NULL going up the stack doesn't look healthy...

backtrace:

NTDLL! 7c918fea()
NTDLL! 7c90104b()
PerlIOUnix_open(interpreter * 0x009ac144, _PerlIO_funcs * 0x280cb548
_PerlIO_unix, PerlIO_list_s * 0x008243cc, long 0, const char *
0x280be25c `string', int 0, int 0, int 0, _PerlIO * * 0x00000000, int 0,
sv * * 0x00000000) line 2633
PerlIOBuf_open(interpreter * 0x00000001, _PerlIO_funcs * 0x280cb708
_PerlIO_crlf, PerlIO_list_s * 0x008243cc, long 1, const char *
0x280be25c `string', int 0, int 0, int 0, _PerlIO * * 0x00000000, int 0,
sv * * 0x00000000) line 3692 + 27 bytes
PerlIO_openn(interpreter * 0x009ac144, const char * 0x00000000, const
char * 0x280be25c `string', int 0, int 0, int 0, _PerlIO * * 0x00000000,
int 0, sv * * 0x00000000) line 1604 + 29 bytes
PerlIO_fdopen(int 0, const char * 0x280be25c `string') line 4995 + 22 bytes
PerlIO_stdstreams(interpreter * 0x009ac144) line 1212
PerlIO_resolve_layers(interpreter * 0x008243cc, const char * 0x00000000,
const char * 0x280b3c5c `string', int 1, sv * * 0x0012fc58) line 1493 +
6 bytes
PerlIO_openn(interpreter * 0x009ac144, const char * 0x00000000, const
char * 0x280b3c5c `string', int -1, int 0, int 0, _PerlIO * *
0x00000000, int 1, sv * * 0x0012fc58) line 1575 + 20 bytes
PerlIO_open(const char * 0x0082443c, const char * 0x280b3c5c `string')
line 5004 + 21 bytes
S_open_script(interpreter * 0x009ac144, const char * 0x0082443c, char 0,
sv * 0x009aebcc, int * 0x0012fce0, _PerlIO * * * 0x0012fcb8) line 3705 +
11 bytes
S_parse_body(interpreter * 0xffffffff, char * * 0x00000000, void
(interpreter *)* 0x10026740 mod_perl_xs_init(interpreter *)) line 2056
perl_parse(interpreter * 0x009ac144, void (interpreter *)* 0x10026740
mod_perl_xs_init(interpreter *), int 2, char * * 0x0012fe20, char * *
0x00000000) line 1651
perl_startup(server_rec * 0x003f8ee8, pool * 0x003f8ec0) line 704 + 27 bytes
perl_module_init(server_rec * 0x003f8ee8, pool * 0x003f8ec0) line 571 +
13 bytes
ap_init_modules(pool * 0x003f8ec0, server_rec * 0x003f8ee8) line 1607 +
4 bytes
post_parse_init() line 7450
apache_main(int 1, char * * 0x00820040) line 7943
main(int 1, char * * 0x00820040) line 33 + 13 bytes
APACHE! mainCRTStartup + 227 bytes
KERNEL32! 7c816d4f()


Philippe M. Chiasson wrote:
> The mod_perl 1.31 release candidate 3 "Works with Perl 5.10" is ready.
> It can be downloaded here:
>
> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc3.tar.gz
>
> MD5: 979059e20febef686e7c2a4d55fe3683
> SHA1: c747ef7d605694ca935795ea7793ea7c77dfa920
>
> The summary of what has changed since 1.30 are (from Changes):
>
> Fix static APACI build against newer apache-1.3.38+
> [Gozer]
>
> Fixed modules/regex.t test 4 on Win32
> [Steve Hay]
>
> Avoid possible segfault when PerlFreshRestart is On.
> [Michael Rendell ]
>
> Prevent segfault when running with perl >= 5.9.3
> [Steve Hay]
>
> Fix shared libary extensions on Win32 to be .dll not .so
> [Nikolay Ananiev ]
>
> Patch to mod_perl.dsp to remove /D _WINSOCK2API_ on Win32
> for perl >= 5.8.6 [Steve Hay]
>

RE: [RELEASE CANDIDATE] mod_perl-1.31 RC3

Philippe M. Chiasson wrote:
> The mod_perl 1.31 release candidate 3 "Works with Perl 5.10" is
> ready. It can be downloaded here:=20
>=20
> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc3.tar.gz

All tests OK here: WinXP SP2, VC6 SP6, Apache 1.3.39 & Perl 5.10.0 (both
built from source).

RE: [RELEASE CANDIDATE] mod_perl-1.31 RC3

Issac Goldstand wrote:
> win32 (xp sp2, vc6 - no SDK upgrade) - Apache 1.41 binary -
> ActivePerl=20
> 5.10 (build 1002)
> FAIL
>=20
> (sorry, folks)
>=20
> Segfault at startup.

I wonder if this is caused by mis-matched CRTs? ActivePerl is built
using VC6 (and therefore uses MSVCRT.dll). You're also using VC6 for
mod_perl, but where did that Apache binary come from? What compiler was
it built with?

Does it work if you build everything yourself from source with the same
compiler?

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC3

Steve Hay wrote:
> Issac Goldstand wrote:
>
>> win32 (xp sp2, vc6 - no SDK upgrade) - Apache 1.41 binary -
>> ActivePerl
>> 5.10 (build 1002)
>> FAIL
>>
>> (sorry, folks)
>>
>> Segfault at startup.
>>
>
> I wonder if this is caused by mis-matched CRTs? ActivePerl is built
> using VC6 (and therefore uses MSVCRT.dll). You're also using VC6 for
> mod_perl, but where did that Apache binary come from? What compiler was
> it built with?
>
> Does it work if you build everything yourself from source with the same
> compiler?
>
I'm reasonably sure that Apache's binaries are still being built with
vc6, which is what prompted me to test this particular set of
prerequisites (since binary Apache + binary ActivePerl will be the
assumed building blocks for a binary PPM package to be installed
upon). Bill, am I wrong about the compiler used for the ASF binary
release of apache-1.3 win32?

I'm going to try to make time over the weekend to build apache +
activeperl from source and see if that changes anything.

Issac

In any case, I'll try to grab ActiveState's source distro and build with
that.

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC3

Issac Goldstand wrote:
>
> I'm reasonably sure that Apache's binaries are still being built with
> vc6, which is what prompted me to test this particular set of
> prerequisites (since binary Apache + binary ActivePerl will be the
> assumed building blocks for a binary PPM package to be installed
> upon). Bill, am I wrong about the compiler used for the ASF binary
> release of apache-1.3 win32?

Nope - you read it correctly; the ASF build is on vc6 (and as this is
the long-dead, and we can only hope - abandoned - 1.3 branch on win32,
that won't ever change).

Bill

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC3

On Thu, 28 Feb 2008, Issac Goldstand wrote:

> Steve Hay wrote:
>> Issac Goldstand wrote:
>>
>>> win32 (xp sp2, vc6 - no SDK upgrade) - Apache 1.41 binary -
>>> ActivePerl 5.10 (build 1002)
>>> FAIL
>>>
>>> (sorry, folks)
>>>
>>> Segfault at startup.
>>
>> I wonder if this is caused by mis-matched CRTs? ActivePerl is built
>> using VC6 (and therefore uses MSVCRT.dll). You're also using VC6 for
>> mod_perl, but where did that Apache binary come from? What compiler was
>> it built with?
>>
>> Does it work if you build everything yourself from source with the same
>> compiler?
>>
> I'm reasonably sure that Apache's binaries are still being built with vc6,
> which is what prompted me to test this particular set of prerequisites (since
> binary Apache + binary ActivePerl will be the assumed building blocks for a
> binary PPM package to be installed upon). Bill, am I wrong about the
> compiler used for the ASF binary release of apache-1.3 win32?

I also got a segfault at startup with ActivePerl 1002
(perl-5.10), using an ASF apache binary and VC++ 6.
All tests passed with the latest ActivePerl 8xx, based on
perl-5.8, using the same Apache binary and compiler.
Steve, is your Perl built using the ActivePerl sources,
with the same compile-time flags as ActivePerl?

--
best regards,
Randy Kobes

RE: [RELEASE CANDIDATE] mod_perl-1.31 RC3

Randy Kobes wrote:
> On Thu, 28 Feb 2008, Issac Goldstand wrote:
>=20
>> Steve Hay wrote:
>>> Issac Goldstand wrote:
>>>=20
>>>> win32 (xp sp2, vc6 - no SDK upgrade) - Apache 1.41 binary -
>>>> ActivePerl 5.10 (build 1002) FAIL
>>>>=20
>>>> (sorry, folks)
>>>>=20
>>>> Segfault at startup.
>>>=20
>>> I wonder if this is caused by mis-matched CRTs? ActivePerl is built
>>> using VC6 (and therefore uses MSVCRT.dll). You're also using VC6 for
>>> mod_perl, but where did that Apache binary come from? What compiler
>>> was it built with?=20
>>>=20
>>> Does it work if you build everything yourself from source with the
>>> same compiler?=20
>>>=20
>> I'm reasonably sure that Apache's binaries are still being built
>> with vc6, which is what prompted me to test this particular set of
>> prerequisites (since binary Apache + binary ActivePerl will be the
>> assumed building blocks for a binary PPM package to be installed
>> upon). Bill, am I wrong about the compiler used for the ASF binary
>> release of apache-1.3 win32?=20
>=20
> I also got a segfault at startup with ActivePerl 1002
> (perl-5.10), using an ASF apache binary and VC++ 6.
> All tests passed with the latest ActivePerl 8xx, based on
> perl-5.8, using the same Apache binary and compiler.
> Steve, is your Perl built using the ActivePerl sources,
> with the same compile-time flags as ActivePerl?

No, mine is built from the "official" 5.10.0 source with my usual
configuration changes (USE_MULTI, USE_ITHREADS, USE_IMP_SYS and
USE_LARGE_FILES switched off, and PERL_MALLOC and DEBUG_MSTATS switched
on).

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC3

Randy, I'm going to start building from scratch using ASF source + AS
source, using default compile options, and we'll see where it goes.
Have I mentioned lately how much I *hate* bootstrapping CPAN (for
prereqs) on Win32? :-p

Issac

Steve Hay wrote:
> Randy Kobes wrote:
>> On Thu, 28 Feb 2008, Issac Goldstand wrote:
>>
>>> Steve Hay wrote:
>>>> Issac Goldstand wrote:
>>>>
>>>>> win32 (xp sp2, vc6 - no SDK upgrade) - Apache 1.41 binary -
>>>>> ActivePerl 5.10 (build 1002) FAIL
>>>>>
>>>>> (sorry, folks)
>>>>>
>>>>> Segfault at startup.
>>>> I wonder if this is caused by mis-matched CRTs? ActivePerl is built
>>>> using VC6 (and therefore uses MSVCRT.dll). You're also using VC6 for
>>>> mod_perl, but where did that Apache binary come from? What compiler
>>>> was it built with?
>>>>
>>>> Does it work if you build everything yourself from source with the
>>>> same compiler?
>>>>
>>> I'm reasonably sure that Apache's binaries are still being built
>>> with vc6, which is what prompted me to test this particular set of
>>> prerequisites (since binary Apache + binary ActivePerl will be the
>>> assumed building blocks for a binary PPM package to be installed
>>> upon). Bill, am I wrong about the compiler used for the ASF binary
>>> release of apache-1.3 win32?
>> I also got a segfault at startup with ActivePerl 1002
>> (perl-5.10), using an ASF apache binary and VC++ 6.
>> All tests passed with the latest ActivePerl 8xx, based on
>> perl-5.8, using the same Apache binary and compiler.
>> Steve, is your Perl built using the ActivePerl sources,
>> with the same compile-time flags as ActivePerl?
>
> No, mine is built from the "official" 5.10.0 source with my usual
> configuration changes (USE_MULTI, USE_ITHREADS, USE_IMP_SYS and
> USE_LARGE_FILES switched off, and PERL_MALLOC and DEBUG_MSTATS switched
> on).

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC3

Built APSource-1002 using default settings and had the same segfault.

Randy Kobes wrote:
> On Thu, 28 Feb 2008, Issac Goldstand wrote:
>
>> Steve Hay wrote:
>>> Issac Goldstand wrote:
>>>
>>>> win32 (xp sp2, vc6 - no SDK upgrade) - Apache 1.41 binary -
>>>> ActivePerl 5.10 (build 1002)
>>>> FAIL
>>>>
>>>> (sorry, folks)
>>>>
>>>> Segfault at startup.
>>>
>>> I wonder if this is caused by mis-matched CRTs? ActivePerl is built
>>> using VC6 (and therefore uses MSVCRT.dll). You're also using VC6 for
>>> mod_perl, but where did that Apache binary come from? What compiler was
>>> it built with?
>>>
>>> Does it work if you build everything yourself from source with the same
>>> compiler?
>>>
>> I'm reasonably sure that Apache's binaries are still being built with
>> vc6, which is what prompted me to test this particular set of
>> prerequisites (since binary Apache + binary ActivePerl will be the
>> assumed building blocks for a binary PPM package to be installed
>> upon). Bill, am I wrong about the compiler used for the ASF binary
>> release of apache-1.3 win32?
>
> I also got a segfault at startup with ActivePerl 1002
> (perl-5.10), using an ASF apache binary and VC++ 6.
> All tests passed with the latest ActivePerl 8xx, based on
> perl-5.8, using the same Apache binary and compiler.
> Steve, is your Perl built using the ActivePerl sources,
> with the same compile-time flags as ActivePerl?
>