perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject Re: need sanity check on my mod_perl + 2.4.6 on Windows attempt
Date Wed, 06 Nov 2013 13:26:45 GMT
On Wed, Nov 6, 2013 at 3:47 AM, Steve Hay <steve.m.hay@googlemail.com>wrote:

> On 6 November 2013 08:44, Steve Hay <steve.m.hay@googlemail.com> wrote:
>
> > Perl XS extensions (like mod_perl) pick up compile and link flags from
> > perl itself. If you're using ActivePerl then they'll be set to
> > "release with debug info" flags. I normally get a debug build by
> > building my own perl:
> >
> > cd win32
> > nmake CFG=Debug INST_TOP=/path/to/install/into
> > nmake CFG=Debug INST_TOP=/path/to/install/into installbare
> >
> > (See win32/Makefile for other settings).
> >
>
> Ah, I should add that you'll want to set CCTYPE=MSVC110 for VC++ 2012,
> and you'll need at least Win32::Process installed into your new perl
> if you go down that route too. That's the only other module *required*
> by mod_perl on Windows (for running the test suite).
>


With the ActiveState Perl, MP_DEBUG=on seems to do the right thing on the
mod_perl build.

-- 
Born in Roswell... married an alien...
http://emptyhammock.com/

Mime
View raw message