Nick *** wrote:
>Hmm, when you build a static httpd/mod_perl, do you tell apache to use
>your preinstalled httpd and not the one in the source. If that's the case,
>then your proposal makes a lot of sense, Nick. If not, then it doesn't,
>since httpd will be linked agaist libapr it will build
> Оригинално писмо
>От: Stas Bekman <[EMAIL PROTECTED]>
>Относно: Re: Some small fixes...
>До: Nick *** <[EMAIL PROTECTED]>
>Изпратено на: Понеделник, 2005, Май 16 17:51:28 EEST
>--
>
>[...]
>
>H
Nick *** wrote:
[...]
>> No, now it picks and install the right stuff and there is no problem
>> with that. The problem is that I want to use MP_AP_PREFIX and
>> MP_AP(R|U)_CONFIG arguments together when building a static MP. Why do
>> I think it's good to have it? Well, my dev machine is a slo
> Оригинално писмо
>От: Stas Bekman <[EMAIL PROTECTED]>
>Относно: Re: Some small fixes...
>До: Nick *** <[EMAIL PROTECTED]>
>Изпратено на: Събота, 2005, Май 14 01:23:14 EEST
>--
>
>Nick *** wrote:
Nick *** wrote:
>> >> Why MP_AP_PREFIX and MP_APR_CONFIG cannot be used together? I guess
>> >> this is valid only when MP_AP_PREFIX is pointing to an installed httpd,
>> >> because when MP_AP_PREFIX is pointing to a source tree, I can get
>> >> around this check by adding MP_AP_CONFIGURE
> Оригинално писмо
>От: Stas Bekman <[EMAIL PROTECTED]>
>Относно: Re: Some small fixes...
>До: Nick *** <[EMAIL PROTECTED]>
>Изпратено на: Петък, 2005, Май 13 00:56:59 EEST
>--
>
>Nick *** wrote:
>&
Nick *** wrote:
>> Why MP_AP_PREFIX and MP_APR_CONFIG cannot be used together? I guess
>> this is valid only when MP_AP_PREFIX is pointing to an installed httpd,
>> because when MP_AP_PREFIX is pointing to a source tree, I can get
>> around this check by adding MP_AP_CONFIGURE="--with-apr=...
>> Why MP_AP_PREFIX and MP_APR_CONFIG cannot be used together? I guess
>> this is valid only when MP_AP_PREFIX is pointing to an installed httpd,
>> because when MP_AP_PREFIX is pointing to a source tree, I can get
>> around this check by adding MP_AP_CONFIGURE="--with-apr=...". It's
>> logi
Nick *** wrote:
>Thanks, committed.
>
>> I didn't use File::Copy, because it's not use(d) at the beginning of
Build.pm, so I thought it isn't loaded.
>
>It should be loaded. I've added the loading.
>
Thanks Stas. Meanwhile I've cooked another patch, but first...
This code in ModPerl::BuildOp
>Thanks, committed.
>
>> I didn't use File::Copy, because it's not use(d) at the beginning of
>> Build.pm, so I thought it isn't loaded.
>
>It should be loaded. I've added the loading.
>
Thanks Stas. Meanwhile I've cooked another patch, but first...
This code in ModPerl::BuildOptions bugs
Nick *** wrote:
btw, any reason why you didn't use perl's link() and File::Copy to do the
work? calling external shell is not a very clean way to code when you have
an API to do that.
Perl's link() on Cygwin seems to copy mod_perl.a to libmod_perl.a, but at this stage mod_perl.a is still a dumm
>>btw, any reason why you didn't use perl's link() and File::Copy to do the
>>work? calling external shell is not a very clean way to code when you have
>>an API to do that.
>Perl's link() on Cygwin seems to copy mod_perl.a to libmod_perl.a, but at this
>stage mod_perl.a is still a dummy lib a
>btw, any reason why you didn't use perl's link() and File::Copy to do the
>work? calling external shell is not a very clean way to code when you have
>an API to do that.
Perl's link() on Cygwin seems to copy mod_perl.a to libmod_perl.a, but at this
stage mod_perl.a is still a dummy lib and
Philip M. Gollucci wrote:
Nick *** wrote:
3. When compiling a static mod_perl and
MP_AP_CONFIGURE="--with-apr=/some/path" argument is given, Apache will
use the apr-config at the given path, but mod_perl will use the default
at "srclib/apr/.libs".
This should be fixed now.
Stas, remember my apr
Nick *** wrote:
3. When compiling a static mod_perl and MP_AP_CONFIGURE="--with-apr=/some/path" argument
is given, Apache will use the apr-config at the given path, but mod_perl will use the default at
"srclib/apr/.libs".
This should be fixed now.
Stas, remember my apr_os_thread_current() issue f
Nick *** wrote:
Hello, it's me again trying to be useful :)
:)
The following patch fixes 3 issues:
1. Fix a warning triggered by `ln` on Cygwin, when running
perl Makefile.PL for a second time without previously running make clean.
committed.
btw, any reason why you didn't use perl's link() and Fil
Hello, it's me again trying to be useful :)
The following patch fixes 3 issues:
1. Fix a warning triggered by `ln` on Cygwin, when running
perl Makefile.PL for a second time without previously running make clean.
2. Show MP_APU_CONFIG as an argument to Makefile.PL in the Usage menu.
3. When compili
17 matches
Mail list logo
