You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Randy Kobes <ra...@theoryx5.uwinnipeg.ca> on 2005/01/05 22:23:39 UTC
can't locate Apache/Build.pm
On Wed, 5 Jan 2005, Ron Savage wrote:
> Server Version: Apache/2.0.50 (Win32) mod_perl/1.99_15-dev Perl/v5.8.4
[ ... ]
> After perl Makefile.PL I get:
> Can't locate Apache/Build.pm in @INC (@INC contains: lib
> C:/Perl/lib C:/Perl/site/lib .) at
> lib/Apache/TestConfig.pm line 33.
Hi Ron,
Just to elaborate - which package (and version) were you
building when this occurred? Also, do you have the Win32
apxs utility (under $APACHE2/bin/) installed? I'll take a
look at this - I've seen similar errors on Win32 in some
contexts. In one case in particular I'm thinking of, this
error was fixed in a recent patch to Apache-Test.
--
best regards,
randy
Re: can't locate Apache/Build.pm
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Fri, 7 Jan 2005, Geoffrey Young wrote:
>
> > 5: Line 30 will return IS_MOD_PERL_2 as true
>
> that should only happen if mod_perl.pm is Apache2/mod_perl.pm. (or if you
> installed mp2 as the only mod_perl on the box...)
>
> > 6: Line 34 will require Apache::Build
> > 7: It must fail because /perl/site/lib/Apache2 is not in @INC
> > and /perl/site/lib/Apache2/Apache/Build.pm is what is being required.
>
> which should be fine, since Apache2.pm has been loaded, otherwise it
> wouldn't have found Apache2/mod_perl.pm... in theory :)
>
> so... if the mod_perl.pm in your standard site_lib is mp2 but everything
> else is under Apache2/ then yeah, it won't work. but that just shouldn't
> happen unless we're doing something wrong with the mp2 install or you
> previously installed mod_perl 2.0 _not_ relative to Apache2 (such as
> MP_INST_APACHE2=0) and things got genuinely borked...
Hi Geoff,
As I mentioned in another reply, the problem with
mod_perl.pm not being under Apache2/ was due to a bug (since
fixed) in mp2 on Win32. Unfortunately, in the binary Ron was
using (that I made up), I didn't notice that the extra
mod_perl.pm not under Apache2/ was still there from an old
install using the broken version, and hence the error. I
apologize for this - it wasn't anything that Ron did, or
didn't, do.
> but let's not get into the Apache2 thing again here,
> please. if there is a real problem with the win32 install
> process then we should fix it. if it's something that is
> being caused by the Apache2 thing that could have been
> solved by installing mp1 in one perl tree and mp2 in
> another perl tree, then it's a userspace issue (for the
> moment). otherwise it's just part of the other discussion
> that we are still trying to solve, in which case thanks so
> much for the detail - we'll be sure to add that to our
> list of cases that should have an obvious resolutionn.
I agree completely about your thoughts on Apache2; the
presence of a bug like this on Win32, especially one that's
been fixed :), shouldn't really be a factor in discussing
the pros and cons.
--
best regards,
randy
Re: can't locate Apache/Build.pm
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
> 5: Line 30 will return IS_MOD_PERL_2 as true
that should only happen if mod_perl.pm is Apache2/mod_perl.pm. (or if you
installed mp2 as the only mod_perl on the box...)
> 6: Line 34 will require Apache::Build
> 7: It must fail because /perl/site/lib/Apache2 is not in @INC
> and /perl/site/lib/Apache2/Apache/Build.pm is what is being required.
which should be fine, since Apache2.pm has been loaded, otherwise it
wouldn't have found Apache2/mod_perl.pm... in theory :)
so... if the mod_perl.pm in your standard site_lib is mp2 but everything
else is under Apache2/ then yeah, it won't work. but that just shouldn't
happen unless we're doing something wrong with the mp2 install or you
previously installed mod_perl 2.0 _not_ relative to Apache2 (such as
MP_INST_APACHE2=0) and things got genuinely borked...
but let's not get into the Apache2 thing again here, please. if there is a
real problem with the win32 install process then we should fix it. if it's
something that is being caused by the Apache2 thing that could have been
solved by installing mp1 in one perl tree and mp2 in another perl tree, then
it's a userspace issue (for the moment). otherwise it's just part of the
other discussion that we are still trying to solve, in which case thanks so
much for the detail - we'll be sure to add that to our list of cases that
should have an obvious resolutionn.
--Geoff
Re: can't locate Apache/Build.pm
Posted by Ron Savage <ro...@savage.net.au>.
On Sat, 8 Jan 2005 09:28:35 -0600 (CST), Randy Kobes wrote:
Hi Randy, Geoff
> Actually, I think this problem arises because in the Win32 binary
> package you're using, I forgot to include a reconfiguration of the
> apxs utility to reflect the location of Apache2. Try reinstalling
> apxs by getting apxs_win32.tar.gz from
> http://perl.apache.org/dist/win32-bin/
> which, when unpacked, has a README that describes how to configure
> and install it.
OK. Here's the situation:
o Downloaded the 28-Dec-04 version of Perl-5.8-win32-bin.exe and apxs_win32.tar.gz
o Installed as per your readmes and my summary [1]
o Everything is working
o There is only 1 file mod_perl.pm
o apxs_win32 must be installed to update c:/apache2/bin/ap* and c:/apache2/build/config_vars.mk stuff
o c:/perl/site/lib/Apache/TestConfigData.pm must be patched manually (change d: to c:) for Apache::Test
[1] http://savage.net.au/Perl/html/upgrade-perl-apache.html
--
Cheers
Ron Savage, ron@savage.net.au on 9/01/2005
http://savage.net.au/index.html
Re: can't locate Apache/Build.pm
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Sat, 8 Jan 2005, Randy Kobes wrote:
> On Sat, 8 Jan 2005, Ron Savage wrote:
> >
> > But now, during nmake test I answer 2 questions, and then get:
> >
> > [warning] running with new config opts:
> > C:\Perl\bin\perl.exe
> > C:\Perl-modules\Apache-Test-1.19\t\TEST
> > -bugreport -verbose=0 -httpd C:\Apache2\bin\Apache.EXE
> > -apxs C:\Apache2\bin\apxs.BAT
> >
> > C:\Perl-modules\Apache-Test-1.19>
> > APXS (C:\Apache2\bin\apxs.BAT) query for SBINDIR failed
> > APXS (C:\Apache2\bin\apxs.BAT) query for TARGET failed
> > APXS (C:\Apache2\bin\apxs.BAT) query for SYSCONFDIR failed
> > APXS (C:\Apache2\bin\apxs.BAT) query for PREFIX failed
[ ... ]
Actually, I think this problem arises because in the Win32
binary package you're using, I forgot to include a
reconfiguration of the apxs utility to reflect the location
of Apache2. Try reinstalling apxs by getting
apxs_win32.tar.gz from
http://perl.apache.org/dist/win32-bin/
which, when unpacked, has a README that describes how
to configure and install it.
--
best regards,
randy
Re: can't locate Apache/Build.pm
Posted by Ron Savage <ro...@savage.net.au>.
On Sat, 8 Jan 2005 00:28:32 -0600 (CST), Randy Kobes wrote:
Hi Randy, Geoff
> No, it definitely should not be like that ... There was a problem
> like this on Win32 (related to apxs needing the PATH environment
> variable set), but that I believe has been fixed with the current
> Apache-Test. To try to track this down, what happens when you do
> C:\> C:\Apache2\bin\apxs.bat -q PREFIX C:\> C:\Apache2\bin\apxs.bat
> -q SBINDIR C:\> C:\Apache2\bin\apxs.bat -q SYSCONFDIR C:\>
> C:\Apache2\bin\apxs.bat -q LIBEXECDIR C:\> C:\Apache2\bin\apxs.bat -
> q TARGET Also, what flavour of Windows are you using? And are you
> using cmd.exe?
Still errors, referring to D:, not C:.
So I edited all references from D: to C: within the 2 files C:\Apache2\bin\apxs.(bat|pl).
Still more errors.
So I edited all references from D: to C: in C:\Apache2\build\config_vars.mk.
Now it (installing Apache::Test V 1.19) finally works :-).
This is Windows 2000, with cmd.exe.
> mod_perl.pm under C:\Perl\site\lib\ was still present. This problem
> (with the binary) has been fixed in the one using Perl-5.8.6/Apache-
> 2.0.52 that I just put out a week or so ago. Sorry for the
> confusion.
OK. I downloaded that yesterday. I'll install it now.
I'll check the files we've discussed and then install Apache::Test V 1.19 just to be sure, and let you know.
Also, I was obviously wrong when I surmised this was an Apache2 namespace problem. Sorry about that.
--
Cheers
Ron Savage, ron@savage.net.au on 9/01/2005
http://savage.net.au/index.html
Re: can't locate Apache/Build.pm
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Sat, 8 Jan 2005, Ron Savage wrote:
> On Fri, 7 Jan 2005 17:07:01 -0600 (CST), Randy Kobes wrote:
>
> Hi Randy, Geoff
>
> >�Thanks for tracking that down .... I think I see what the problem
> >�is (and I've been bitten by that before) - line 30 of
> >�Apache::TestConfig is erroneously setting MOD_PERL_2 as true
> >�because (I suspect) you have a stray mod_perl.pm under
> >�C:\Perl\site\lib\ from an earlier install (on Win32, there was a
> >�bug in older mp2 installs that not all the files were correctly put
> >�under Apache2/ - the proper place for mod_perl.pm should be under
> >�C:\Perl\site\lib\Apache2\).
>
> I had 2 copies of mod_perl.pm, in the places you've
> specified. I removed the one in /perl/site/lib.
>
> But now, during nmake test I answer 2 questions, and then get:
>
> [warning] running with new config opts:
> C:\Perl\bin\perl.exe
> C:\Perl-modules\Apache-Test-1.19\t\TEST
> -bugreport -verbose=0 -httpd C:\Apache2\bin\Apache.EXE
> -apxs C:\Apache2\bin\apxs.BAT
>
> C:\Perl-modules\Apache-Test-1.19>
> APXS (C:\Apache2\bin\apxs.BAT) query for SBINDIR failed
> APXS (C:\Apache2\bin\apxs.BAT) query for TARGET failed
> APXS (C:\Apache2\bin\apxs.BAT) query for SYSCONFDIR failed
> APXS (C:\Apache2\bin\apxs.BAT) query for PREFIX failed
[ ... ]
> (and again, for each test, until finally)
>
> All tests successful.
> Files=5, Tests=21, 18 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 CPU)
> [warning] server ron:8529 shutdown
> [Here I have to hit enter to get the prompt back]
> C:\Perl-modules\Apache-Test-1.19>
>
> I can't imagine this to be what's meant to happen.
No, it definitely should not be like that ... There was a
problem like this on Win32 (related to apxs needing the PATH
environment variable set), but that I believe has been fixed
with the current Apache-Test. To try to track this down,
what happens when you do
C:\> C:\Apache2\bin\apxs.bat -q PREFIX
C:\> C:\Apache2\bin\apxs.bat -q SBINDIR
C:\> C:\Apache2\bin\apxs.bat -q SYSCONFDIR
C:\> C:\Apache2\bin\apxs.bat -q LIBEXECDIR
C:\> C:\Apache2\bin\apxs.bat -q TARGET
Also, what flavour of Windows are you using? And
are you using cmd.exe?
> Just to recap, this is an Apache-Perl (V 5.8.4) prepared
> by you (Randy), with no additional Apache modules
> installed by me, so when you say 'an older mp2 install' it
> isn't that old! Are you sure this has been fixed?
Sorry, I should have been clearer ... The Apache/Perl Win32
binary that you're using had an old mod_perl installed (by
me) that suffered from a bug that didn't place mod_perl.pm
under C:\Perl\site\lib\Apache2\. This was fixed, and I used
that mod_perl in the binary you're using. However, I didn't
notice that the stray mod_perl.pm under C:\Perl\site\lib\
was still present. This problem (with the binary) has been
fixed in the one using Perl-5.8.6/Apache-2.0.52 that I
just put out a week or so ago. Sorry for the confusion.
--
best regards,
randy
Re: can't locate Apache/Build.pm
Posted by Ron Savage <ro...@savage.net.au>.
On Fri, 7 Jan 2005 17:07:01 -0600 (CST), Randy Kobes wrote:
Hi Randy, Geoff
> Thanks for tracking that down .... I think I see what the problem
> is (and I've been bitten by that before) - line 30 of
> Apache::TestConfig is erroneously setting MOD_PERL_2 as true
> because (I suspect) you have a stray mod_perl.pm under
> C:\Perl\site\lib\ from an earlier install (on Win32, there was a
> bug in older mp2 installs that not all the files were correctly put
> under Apache2/ - the proper place for mod_perl.pm should be under
> C:\Perl\site\lib\Apache2\). If that's the case, and also assuming
> you have
> C:\Perl\site\lib\Apache2\mod_perl.pm (if not, it will be placed
> there by the current mp2 install), try removing
> C:\Perl\site\lib\mod_perl.pm and try Apache-Test again.
I had 2 copies of mod_perl.pm, in the places you've specified. I removed the one in /perl/site/lib.
But now, during nmake test I answer 2 questions, and then get:
[warning] running with new config opts: C:\Perl\bin\perl.exe C:\Perl-modules\Apache-Test-1.19\t\TEST
-bugreport -verbose=0 -httpd C:\Apache2\bin\Apache.EXE -apxs C:\Apache2\bin\apxs.BAT
C:\Perl-modules\Apache-Test-1.19>APXS (C:\Apache2\bin\apxs.BAT) query for SBINDIR failed
APXS (C:\Apache2\bin\apxs.BAT) query for TARGET failed
APXS (C:\Apache2\bin\apxs.BAT) query for SYSCONFDIR failed
APXS (C:\Apache2\bin\apxs.BAT) query for PREFIX failed
(about 26 of that last line, then)
APXS (C:\Apache2\bin\apxs.BAT) query for LIBEXECDIR failed
APXS (C:\Apache2\bin\apxs.BAT) query for LIBEXECDIR failed
C:/Apache2/bin/Apache.EXE -d C:/Perl-modules/Apache-Test-1.19/t -f C:/Perl-modules/Apache-Test-1.19
/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS
using Apache/2.0.50 (winnt MPM)
waiting 60 seconds for server to start: ...
waiting 60 seconds for server to start: ok (waited 2 secs)
server ron:8529 started
t\bad_coding....APXS (C:\Apache2\bin\apxs.BAT) query for SBINDIR failed
APXS (C:\Apache2\bin\apxs.BAT) query for SYSCONFDIR failed
APXS (C:\Apache2\bin\apxs.BAT) query for PREFIX failed
(again about 26 of that last, then)
APXS (C:\Apache2\bin\apxs.BAT) query for PREFIX failed
t\bad_coding....ok
t\cookies.......APXS (C:\Apache2\bin\apxs.BAT) query for SBINDIR failed
APXS (C:\Apache2\bin\apxs.BAT) query for SYSCONFDIR failed
APXS (C:\Apache2\bin\apxs.BAT) query for PREFIX failed
(and again, for each test, until finally)
t\request.......ok
All tests successful.
Files=5, Tests=21, 18 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 CPU)
[warning] server ron:8529 shutdown
[Here I have to hit enter to get the prompt back]
C:\Perl-modules\Apache-Test-1.19>
I can't imagine this to be what's meant to happen.
Just to recap, this is an Apache-Perl (V 5.8.4) prepared by you (Randy), with no additional Apache modules installed by me, so when you say 'an older mp2 install' it isn't that old! Are you sure this has been fixed?
I have a program which will install all the modules I use, so blowing the lot away and re-installing - just to see what happens -, although a pain, is possible, if doing so would help.
But then, I might as well upgrade, if you have a newer A-P package available.
--
Cheers
Ron Savage, ron@savage.net.au on 8/01/2005
http://savage.net.au/index.html
Re: can't locate Apache/Build.pm
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Sat, 8 Jan 2005, Ron Savage wrote:
> Hi Randy
>
> Observe the error msg again:
>
> C:\Perl-modules\Apache-Test-1.19>perl Makefile.PL
> Can't locate Apache/Build.pm in @INC (@INC contains: lib C:/Perl/lib C:/Perl/site/lib .) at lib/Apac
> he/TestConfig.pm line 33.
> BEGIN failed--compilation aborted at lib/Apache/TestConfig.pm line 34.
> Compilation failed in require at lib/Apache/TestMM.pm line 21.
> BEGIN failed--compilation aborted at lib/Apache/TestMM.pm line 21.
> Compilation failed in require at Makefile.PL line 17.
> BEGIN failed--compilation aborted at Makefile.PL line 17.
>
> The sequence of events is:
> 1: Run Makefile.PL
> 2: Execute line 17 of Makefile.PL:
> use Apache::TestMM qw(test clean); #enable 'make test and make clean'
> 3: Execute line 21 of TestMM:
> use Apache::TestConfig ();
> (which incidentally is the same as line 21 of Makefile.PL, so both need to work)
> 4: Execute lines 30 .. 34 of TestConfig:
> 5: Line 30 will return IS_MOD_PERL_2 as true
> 6: Line 34 will require Apache::Build
> 7: It must fail because /perl/site/lib/Apache2 is not in @INC
> and /perl/site/lib/Apache2/Apache/Build.pm is what is being required.
Hi Ron,
Thanks for tracking that down .... I think I see what
the problem is (and I've been bitten by that before) - line
30 of Apache::TestConfig is erroneously setting MOD_PERL_2
as true because (I suspect) you have a stray mod_perl.pm
under C:\Perl\site\lib\ from an earlier install (on Win32,
there was a bug in older mp2 installs that not all the files
were correctly put under Apache2/ - the proper place for
mod_perl.pm should be under C:\Perl\site\lib\Apache2\). If
that's the case, and also assuming you have
C:\Perl\site\lib\Apache2\mod_perl.pm (if not, it will be
placed there by the current mp2 install), try removing
C:\Perl\site\lib\mod_perl.pm and try Apache-Test again.
--
best regards,
randy
Re: can't locate Apache/Build.pm
Posted by Ron Savage <ro...@savage.net.au>.
On Thu, 6 Jan 2005 17:42:29 -0600 (CST), Randy Kobes wrote:
Hi Randy
> Very strange :( If you completely hide any previous Apache::Test*
> modules that may have been installed, and start from a clean source
> distribution, does building it manually run into the same problem?
No difference after moving /perl/site/lib/Apache/Test* to /temp.
Observe the error msg again:
C:\Perl-modules\Apache-Test-1.19>perl Makefile.PL
Can't locate Apache/Build.pm in @INC (@INC contains: lib C:/Perl/lib C:/Perl/site/lib .) at lib/Apac
he/TestConfig.pm line 33.
BEGIN failed--compilation aborted at lib/Apache/TestConfig.pm line 34.
Compilation failed in require at lib/Apache/TestMM.pm line 21.
BEGIN failed--compilation aborted at lib/Apache/TestMM.pm line 21.
Compilation failed in require at Makefile.PL line 17.
BEGIN failed--compilation aborted at Makefile.PL line 17.
The sequence of events is:
1: Run Makefile.PL
2: Execute line 17 of Makefile.PL:
use Apache::TestMM qw(test clean); #enable 'make test and make clean'
3: Execute line 21 of TestMM:
use Apache::TestConfig ();
(which incidentally is the same as line 21 of Makefile.PL, so both need to work)
4: Execute lines 30 .. 34 of TestConfig:
5: Line 30 will return IS_MOD_PERL_2 as true
6: Line 34 will require Apache::Build
7: It must fail because /perl/site/lib/Apache2 is not in @INC
and /perl/site/lib/Apache2/Apache/Build.pm is what is being required.
When I search CPAN for Apache::Build, thinking to install it alone and see if it can be put in /perl/site/lib, I get:
mod_perl-2.0.0-RC3 - 05 Jan 2005 - Philippe M. Chiasson, so that ain't gunna work either.
> Additionally, if you install the newest version of Apache-Test, and
> then try building Apache-Test from the sources, does the same
> problem result?
No can do.
--
Cheers
Ron Savage, ron@savage.net.au on 8/01/2005
http://savage.net.au/index.html
Re: can't locate Apache/Build.pm
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Fri, 7 Jan 2005, Ron Savage wrote:
> On Thu, 6 Jan 2005 11:43:30 -0600 (CST), Randy Kobes wrote:
[ ... ]
> >A new version (1.19) was just uploaded:
> >http://www.cpan.org/authors/id/G/GO/GOZER/
> >Could you try this one to see if you get the same problem? I just
> > tried it and it seemed to work OK.
>
> Same error with 1.19
>
> > If you still get the same problem, do you have a
> > $PERL\site\lib\Apache\TestConfigData.pm
> > installed in your Perl tree? If so, does moving it out of the way,
>
> Yes. I removed it and got the same error.
>
> > and then building Apache-Test, work? In building Apache-Test you
> > should then be taken through a dialogue asking you where your
>
> No dialog, but I'm running this install from with a Perl program...
> I'll now try from the command line.
>
> > Apache executable is located (if it can't find it), but this
> > information should then be saved to Apache::TestConfigData, which
> > gets installed for future use.
>
> Nope. I get the error (Can't locate Apache/Build.pm in
> @INC) as soon as I type perl Makefile.PL, so there is no
> opportunity for code to run to ask any questions.
Very strange :( If you completely hide any previous
Apache::Test* modules that may have been installed, and
start from a clean source distribution, does building
it manually run into the same problem?
Additionally, if you install the newest version of
Apache-Test, and then try building Apache-Test from
the sources, does the same problem result?
--
best regards,
randy
Re: can't locate Apache/Build.pm
Posted by Ron Savage <ro...@savage.net.au>.
On Thu, 6 Jan 2005 11:43:30 -0600 (CST), Randy Kobes wrote:
Hi Randy
>> Just to elaborate - which package (and version) were you building
>> when this occurred?
>>
Apache::Test V 1.18 for those who missed it
>
> I understand now this was with the Apache-Test distribution itself.
> A new version (1.19) was just uploaded:
> http://www.cpan.org/authors/id/G/GO/GOZER/
> Could you try this one to see if you get the same problem? I just
> tried it and it seemed to work OK.
Same error with 1.19
> If you still get the same problem, do you have a
> $PERL\site\lib\Apache\TestConfigData.pm
> installed in your Perl tree? If so, does moving it out of the way,
Yes. I removed it and got the same error.
> and then building Apache-Test, work? In building Apache-Test you
> should then be taken through a dialogue asking you where your
No dialog, but I'm running this install from with a Perl program...
I'll now try from the command line.
> Apache executable is located (if it can't find it), but this
> information should then be saved to Apache::TestConfigData, which
> gets installed for future use.
Nope. I get the error (Can't locate Apache/Build.pm in @INC) as soon as I type perl Makefile.PL,
so there is no opportunity for code to run to ask any questions.
--
Cheers
Ron Savage, ron@savage.net.au on 7/01/2005
http://savage.net.au/index.html
Re: can't locate Apache/Build.pm
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Wed, 5 Jan 2005, Randy Kobes wrote:
> On Wed, 5 Jan 2005, Ron Savage wrote:
>
> > Server Version: Apache/2.0.50 (Win32) mod_perl/1.99_15-dev Perl/v5.8.4
> [ ... ]
> > After perl Makefile.PL I get:
> > Can't locate Apache/Build.pm in @INC (@INC contains: lib
> > C:/Perl/lib C:/Perl/site/lib .) at
> > lib/Apache/TestConfig.pm line 33.
>
> Just to elaborate - which package (and version) were you
> building when this occurred?
I understand now this was with the Apache-Test distribution
itself. A new version (1.19) was just uploaded:
http://www.cpan.org/authors/id/G/GO/GOZER/
Could you try this one to see if you get the same problem?
I just tried it and it seemed to work OK.
If you still get the same problem, do you have a
$PERL\site\lib\Apache\TestConfigData.pm
installed in your Perl tree? If so, does moving it out of
the way, and then building Apache-Test, work? In building
Apache-Test you should then be taken through a dialogue
asking you where your Apache executable is located (if it
can't find it), but this information should then be saved to
Apache::TestConfigData, which gets installed for future use.
--
best regards,
randy