You need to build perl yourself using VC/nmake too or else find some other binary build using VC/nmake because ActivePerl actually uses gcc/dmake just like Strawberry Perl these days...
On 6 October 2014 15:23, Mathieu Simon <mathieu....@gmail.com> wrote: > Hi > > 2014-10-02 10:27 GMT+02:00 Mathieu Simon <mathieu....@gmail.com>: >>> >>> >> Aha, so I guess a Visual Studio is required then? >> Let me give it a whirl then. :-) > > So I had the oppoortunity to give this a bit a test and from what I looks > now > the situation is a bit in dare state for building mod_perl for httpd 2.4.x > on Windows > > - Strawberry Perl fails for mod_perl since its toolchain mostly relies on > dmake > (as previously said, not really working for mod_perl) > > - I was able to obtain a (seemingly) apxs_win32 from Apachelounge* > -> without it you get the said error with both Windows Perl > distributions. > > I focussed then on ActivePerl 5.18 since that one seems to be more closely > tied to VC - ? > > - ActivePerl 5.18 at least contains ExtUtils:Embed 1.3001 > (still fails initially but can be silenced by 'set > MP_USE_MY_EXTUTILS_EMBED=1) > - Within the "VS2012 x86 Natvie Tools Command Prompt" and a apxs.bat 'perl > Makefile.pl' > passes with some errors. (some progress at least!) > - However the resulting Makefile doesn't take take care of the Windows > environment as it wants to use dmake and gcc > > I'm not enough familiar with MakeMaker - any hint how to get further? I > compared on a Ubuntu VM > where the SVN HEAD builds properly without issues, so it is a > Windows-specific problem. > > Best regards > Mat > > * https://www.apachelounge.com/download/additional/
