perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sergeant <m...@sergeant.org>
Subject Re: AxKit working on ActivePerl
Date Fri, 01 Sep 2000 17:26:36 GMT
On Fri, 1 Sep 2000, Randy Kobes wrote:

> On Fri, 1 Sep 2000, Matt Sergeant wrote:
> 
> > Well it seems to be working. Like Randy, I too haven't done much stress
> > testing, and in fact haven't even done much no-stress testing, I just
> > wanted to get a mail out saying I managed to compile it.
> > 
> > To get it to compile I had to remove a define (PERL_IMPLICIT_SYS) and add
> > three defines (_MSWSOCK_, _WINSOCK2API_ and _WINDOWS (for the errors in
> > malloc.h)), 
> 
> That also fixes the problems building Embperl, although there's
> then some warnings, and not all the tests pass. I had also tried,
> as an alternative to undefining PERL_IMPLICIT_SYS and defining _WINDOWS,
> defining _INC_MALLOC and _INC_SIGNAL, which also seems to work.
>  
> >            and a whole bunch of link problems - it wouldn't seem to link
> > to ApacheModulePerl.lib, so I had to add every damn .obj file in that
> > directory (src/modules/ApacheModulePerl/Release) in for it to link to.
> > After that it worked. Everything seems to run like a charm.
> 
> The linking problems I also found with libapreq on Win32,
> on a non-ActiveState build, and I had to do the same thing as you.
> So it might be worth looking at the build of ApacheModulePerl.lib,
> to see if this can be fixed there.

I wonder if its to do with name mangling, because the symbols that were
missing didn't show up in AMP.lib.

I didn't have any trouble with libapreq, how odd...

> 
> > 
> > More testing to do, obviously, but I think we have a winner here.
> > 
> > Should we offer up a fully compiled Apache + mod_perl installation? Or
> > just a ppm with a post-install script (done that before) that asks for and
> > installs ApacheModulePerl.dll in the right place? Obviously Randy seems to
> > have cooked up most of the ppm, but without the install of the
> > ApacheModulePerl.dll thing. Adding that is mostly trivial.
> 
> I'm not sure if ActiveState would add Apache::* ppds to their
> list - perhaps not, as it would be more difficult to keep in
> sync with Apache. We could set up a ppm site with a bunch of
> Apache ppds - with the working mod_perl, many could be placed
> there immediately. The post-install script for ApacheModulePerl.dll
> is a good idea ... These ppds should be compatable with
> Apache's 1.3.12 binary, although we could make up an all-in-one
> package for the impatient ....

I'm busy this weekend (wedding), so maybe you could take a look at the
post-install thing. It works directly from MakeMaker's POST_INSTALL (I
think thats the right option), and nmake ppd does all the right
things. Also see NNML's ppd file/distribution, which is where I found out
you could do that. (NNML is in AS's PPM repository).

-- 
<Matt/>

Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org


Mime
View raw message