Steve Hay wrote:
[...]
What other misleading parts are we talking about?
I'm just getting confused with changes in Apache itself, I think.
Apache 1 used to have "lib", "libexec" and "modules": "lib" stored the
static .lib's, "libexec" stored the import libraries for various dll's,
and "modul
Stas Bekman wrote:
Steve Hay wrote:
[...]
Having a pointer to where the mod_perl.lib library was
installed would be useful. I'm not sure calling it
MODPERL_STATIC_LIB_LOCATION would be the best thing on
Win32, as it's not a static library as such, but something
could be come up with ...
Well,
Steve Hay wrote:
[...]
Having a pointer to where the mod_perl.lib library was
installed would be useful. I'm not sure calling it
MODPERL_STATIC_LIB_LOCATION would be the best thing on
Win32, as it's not a static library as such, but something
could be come up with ...
Well, if ModPerl::MM does th
Stas Bekman wrote:
Randy Kobes wrote:
On Fri, 12 Sep 2003, Stas Bekman wrote:
Steve Hay wrote:
Stas Bekman wrote:
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
I believe that mod_perl 2 now installs the mod_perl.lib
somewhere to solve that kind of problem. Is there an
option in
Randy Kobes wrote:
On Fri, 12 Sep 2003, Stas Bekman wrote:
Steve Hay wrote:
Stas Bekman wrote:
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
I believe that mod_perl 2 now installs the mod_perl.lib
somewhere to solve that kind of problem. Is there an
option in the mod_perl 1 build
On Fri, 12 Sep 2003, Stas Bekman wrote:
> Steve Hay wrote:
> > Stas Bekman wrote:
> >> Randy Kobes wrote:
> >>> On Fri, 12 Sep 2003, Steve Hay wrote:
> I believe that mod_perl 2 now installs the mod_perl.lib
> somewhere to solve that kind of problem. Is there an
> option in the mod
Steve Hay wrote:
Stas Bekman wrote:
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
I believe that mod_perl 2 now installs the mod_perl.lib
somewhere to solve that kind of problem. Is there an
option in the mod_perl 1 build process to thave that
library installed, or could that be add
Stas Bekman wrote:
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
I believe that mod_perl 2 now installs the mod_perl.lib
somewhere to solve that kind of problem. Is there an
option in the mod_perl 1 build process to thave that
library installed, or could that be added to the next
re
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
Randy Kobes wrote:
[ .. ]
Here's a patch against the Apache-Dispatch Makefile.PL to
allow it to build on Win32
Your patch does the trick for me, except that I had to
rebuild mod_perl too.
The problem is that my installed mod_perl setup (Ap
On Fri, 12 Sep 2003, Steve Hay wrote:
> Randy Kobes wrote:
[ .. ]
> >Here's a patch against the Apache-Dispatch Makefile.PL to
> >allow it to build on Win32
> >
> Your patch does the trick for me, except that I had to
> rebuild mod_perl too.
>
> The problem is that my installed mod_perl setup (Apa
Randy Kobes wrote:
On Thu, 11 Sep 2003, Geoffrey Young wrote:
The problem you described before with the missing symbols
can be resolved by linking against the mod_perl.lib built
when you build mod_perl.so. This can be done by adding in
a LIBS attribute to WriteMakefile() in Makefile.PL with a
Hi!
On Thu, Sep 11, 2003 at 10:24:20PM -0500, Randy Kobes wrote:
> Here's a patch against the Apache-Dispatch Makefile.PL to
> allow it to build on Win32 - I've also put up a ppm package
Oh, great! Thanks Randy! I'll put this into the next release, which should
happen in a few days...
--
#!/us
On Thu, 11 Sep 2003, Geoffrey Young wrote:
>
> > The problem you described before with the missing symbols
> > can be resolved by linking against the mod_perl.lib built
> > when you build mod_perl.so. This can be done by adding in
> > a LIBS attribute to WriteMakefile() in Makefile.PL with a
> > v
The problem you described before with the missing symbols
can be resolved by linking against the mod_perl.lib built
when you build mod_perl.so. This can be done by adding in
a LIBS attribute to WriteMakefile() in Makefile.PL with a
value of ' -L/Path/to/mod_perl_lib -lmod_perl'.
ah, right. thanks
On Thu, 11 Sep 2003, Steve Hay wrote:
> Thomas Klausner wrote:
>
> >On Thu, Sep 11, 2003 at 08:33:31AM +0100, Steve Hay wrote:
> >
> >>I posted this problem the other day, deep inside a
> >>thread about something else, and didn't get any replies;
> >>maybe nobody spotted it?
> >>
> >>Does anybody
Hi!
On Thu, Sep 11, 2003 at 08:59:23AM +0100, Steve Hay wrote:
> I would rather be able to build the module myself anyway, rather than
> using a PPM package.
I guess (and Geoffrey (who BTW transfered maintainership of Apache::Dispatch
to me..) suggested something) the problem lies within the cu
Thomas Klausner wrote:
Hi!
On Thu, Sep 11, 2003 at 08:33:31AM +0100, Steve Hay wrote:
I posted this problem the other day, deep inside a thread about
something else, and didn't get any replies; maybe nobody spotted it?
Does anybody have Apache::Dispatch working on Windows with Perl 5.8.0?
Hi!
On Thu, Sep 11, 2003 at 08:33:31AM +0100, Steve Hay wrote:
> I posted this problem the other day, deep inside a thread about
> something else, and didn't get any replies; maybe nobody spotted it?
>
> Does anybody have Apache::Dispatch working on Windows with Perl 5.8.0?
> Randy?
Randy p
Hi,
I posted this problem the other day, deep inside a thread about
something else, and didn't get any replies; maybe nobody spotted it?
Does anybody have Apache::Dispatch working on Windows with Perl 5.8.0?
Randy?
I'm trying to build it on Windows XP (MSVC++ 6) with Perl 5.8.0 / Apache
1.3
19 matches
Mail list logo
