Stas has fixed this up in the cvs version, by delaying the
loading of Archive::Tar (and LWP) until they're needed. If
the apxs utilities are already present, it should just exit
from this script immediately, once it finds them, and
continue along.
And that fix was included in 1.99_11 which was jus
The URL
http://perl.apache.org/~geoff/mod_perl-1.99_11.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GE/GEOFF/mod_perl-1.99_11.tar.gz
size: 1093014 bytes
md5: 855adb033de193dc999a5a2bd714f675
Changes since 1.99_10
add a build/win32_fetch_apxs script (called within the top-level
The URL
http://perl.apache.org/~geoff/Apache-Test-1.06.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GE/GEOFF/Apache-Test-1.06.tar.gz
size: 94492 bytes
md5: 27c7096b027fa1d477b260c54d49c455
Changes since 1.05
added -startup_timeout and $ENV{APACHE_TEST_STARTUP_TIMEOUT} as place
On Mon, 10 Nov 2003, Steve Hay wrote:
> Geoffrey Young wrote:
>
> >a release candidate for mod_perl 1.99_11 is now available
> >for testing. note that 1.99_11 will be required for
> >users running perl 5.8.2.
> >
> >please grab the candidate from
> >
> > http://perl.apache.org/~geoff/mod_perl-1
Rafael Garcia-Suarez wrote:
Stas Bekman wrote:
I've suggested that long time ago and we have discussed the idea here. It
can't work the way you (and I) suggested. Since PerlLoadModule loads things
into *the* interpreter that you will need to access later during the request
time. Same goes for .
Geoffrey Young wrote:
hmm... so wildcards are in by default on gentoo. does anyone else
know of other standard distributions that use wildcards? I certainly
don't want the warning to raise lots of eyebrows and suspicions...
what we could do is to try to expand it with <> and if at least one
hmm... so wildcards are in by default on gentoo. does anyone else
know of other standard distributions that use wildcards? I certainly
don't want the warning to raise lots of eyebrows and suspicions...
what we could do is to try to expand it with <> and if at least one file
exist copy it ov
Stas Bekman wrote:
>
> I've suggested that long time ago and we have discussed the idea here. It
> can't work the way you (and I) suggested. Since PerlLoadModule loads things
> into *the* interpreter that you will need to access later during the request
> time. Same goes for . What you really ne
Geoffrey Young wrote:
Haroon Rafique wrote:
On Today at 12:11pm, GY=>Geoffrey Young <[EMAIL PROTECTED]>
wrote:
GY> GY> ok, that's just a warning. I assume that is the target of an
Include
GY> directive in your default httpd.conf?
GY>
That's correct. I found the following line in the apache2
Steve Hay wrote:
[...]
I've haven't had time to look into this yet, but when I ran "perl
Makefile.PL MP_AP_PREFIX=C:/apache2" using a fresh perl-5.8.2 build with
only libwin32 and IPC-Run3 added, it complained that Archive-Tar was not
present.
My apologies if I'm guessing wrong, but it looked l
Geoffrey Young wrote:
[...]
So, in the worker mpm, you need to load as little as possible before
cloning, and only load modules when they are really needed inside the
thread. This is perpendicular to prefork mpm, where you want to load
as much as possible beforehand.
The problem is with 3rd p
Geoffrey Young wrote:
>a release candidate for mod_perl 1.99_11 is now available for testing. note
>that 1.99_11 will be required for users running perl 5.8.2.
>
>please grab the candidate from
>
> http://perl.apache.org/~geoff/mod_perl-1.99_11-dev.tar.gz
>[snip]
>
>Changes since 1.99_10:
>
>a
Haroon Rafique wrote:
On Today at 12:11pm, GY=>Geoffrey Young <[EMAIL PROTECTED]> wrote:
GY>
GY> ok, that's just a warning. I assume that is the target of an Include
GY> directive in your default httpd.conf?
GY>
That's correct. I found the following line in the apache2.conf file
(supplied by
the behavior hasn't changed since
1.99_10 but it now emits a warning if it can't properly resolve a target
file
yike, it has changed - my bad.
try this patch. it still will give you the warning, but now it behaves like
it used to. I may end up changing the warning to a debug message I think
The code which figured out where the installed apache 2 config files are
located used to work flawlessly in 1.99_10. Now I get a:
*** configuration file /etc/apache2/conf/modules.d/*.conf does not exist
fairly early in the configuration process.
ok, that's just a warning. I assume that is the
This may be old news to some, but I wrote an article about this about
two months ago on Perlmonks: Things you need to know before
programming Perl ithreads.
http://www.perlmonks.org/index.pl?node_id=288022
Yup, you kindly pointed me to it when you wrote it. It's a very good
article.
I had
16 matches
Mail list logo
