On Mon, 10 Sep 2001, Stas Bekman wrote:
But then in case we have the static built make will attempt to install .so
which doesn't exist. So should we then check against MP_USE_DSO?
yeah, that's fine.
-
To unsubscribe,
On Sun, 9 Sep 2001, Doug MacEachern wrote:
On Mon, 10 Sep 2001, Stas Bekman wrote:
But then in case we have the static built make will attempt to install .so
which doesn't exist. So should we then check against MP_USE_DSO?
yeah, that's fine.
there is only one bit left, how do I make
On Sat, 8 Sep 2001, Doug MacEachern wrote:
On Sat, 8 Sep 2001, Stas Bekman wrote:
I've tried to use Apache-Test outside of modperl, but the server won't
find libmodperl.so, since it wasn't installed on my system on 'make
install'. Is this on purpose? I see ModPerl::MM::install is
On Mon, 10 Sep 2001, Stas Bekman wrote:
should we change the default log level to notice in Apache::TestTrace?
Using warning for things like: installing foo doesn't seem right.
we should let make/MakeMaker take care of those messages.
not sure how clean is this patch, but it installs the
On Sun, 9 Sep 2001, Doug MacEachern wrote:
On Mon, 10 Sep 2001, Stas Bekman wrote:
should we change the default log level to notice in Apache::TestTrace?
Using warning for things like: installing foo doesn't seem right.
we should let make/MakeMaker take care of those messages.
not
On Mon, 10 Sep 2001, Stas Bekman wrote:
the problem is that $code-generate($build); is running in
post_configure(), which means that I don't know $libmodperl (which is
$build-{'MODPERL_LIB'}) during MY::post_initialize.
oh right. you can use this instead:
join '.', $build-{MP_LIBNAME},
On Sun, 9 Sep 2001, Doug MacEachern wrote:
On Mon, 10 Sep 2001, Stas Bekman wrote:
the problem is that $code-generate($build); is running in
post_configure(), which means that I don't know $libmodperl (which is
$build-{'MODPERL_LIB'}) during MY::post_initialize.
oh right. you can use
On Mon, 10 Sep 2001, Stas Bekman wrote:
But MODPERL_LIB will have .a extension if we make a static build. and
$Config{dlext} hardcodes dynamic lib extension. Or we don't care now?
we should only install the .so, libmodperl.a is only useful when linked
into httpd.
another thing I'm not
On Sun, 9 Sep 2001, Doug MacEachern wrote:
On Mon, 10 Sep 2001, Stas Bekman wrote:
But MODPERL_LIB will have .a extension if we make a static build. and
$Config{dlext} hardcodes dynamic lib extension. Or we don't care now?
we should only install the .so, libmodperl.a is only useful when
I've tried to use Apache-Test outside of modperl, but the server won't
find libmodperl.so, since it wasn't installed on my system on 'make
install'. Is this on purpose? I see ModPerl::MM::install is supposed to do
that, but it doesn't end up in Makefile. Or do I miss something?
I've manually
On Sat, 8 Sep 2001, Stas Bekman wrote:
I've tried to use Apache-Test outside of modperl, but the server won't
find libmodperl.so, since it wasn't installed on my system on 'make
install'. Is this on purpose? I see ModPerl::MM::install is supposed to do
that, but it doesn't end up in
11 matches
Mail list logo
