Hi Folks,
I'm trying to get A::T running under Windows. Besides the recent rash of
troubles I've had with TestRun.pm, my tests are successfully running
under Linux.
Here's the error message I'm receiving when running `make test`:
[ error] configure() has failed:
Can't locate mod_perl.pm in
William McKee wrote:
On Thu, Mar 11, 2004 at 04:25:42PM -0800, Stas Bekman wrote:
OK, please let us know once you get a clean build and if it's still failing
we will take it from there. Thanks.
OK, finally got Perl 5.8.3 properly built. Unfortunately, my tests are
still failing. However, this
On Fri, Mar 12, 2004 at 05:26:05PM -0800, Stas Bekman wrote:
I suspect that you are subclassing ModPerl::TestRun instead of
Apache::TestRun. The former requires mod_perl, the latter doesn't not.
ModPerl::TestRun is a subclass of Apache::TestRun
This would be in the TEST.PL file, right? Here's
William McKee wrote:
On Fri, Mar 12, 2004 at 05:26:05PM -0800, Stas Bekman wrote:
I suspect that you are subclassing ModPerl::TestRun instead of
Apache::TestRun. The former requires mod_perl, the latter doesn't not.
ModPerl::TestRun is a subclass of Apache::TestRun
This would be in the TEST.PL
On Fri, Mar 12, 2004 at 07:01:29PM -0800, Stas Bekman wrote:
Why do you have /usr/lib/libperl.* at all? It's a bad idea to have it in
the common path if you have more than one perl installed on the same system.
Yes, you always need to rebuild mod_perl with the new version of perl.
I must
On Fri, Mar 12, 2004 at 07:18:38PM -0800, Stas Bekman wrote:
No, that's fine. I should have looked at Apache/TestConfigPerl.pm line
486. It runs that code if you have mod_perl tests. i.e. response module
t/response/TestFoo/Bar.pm.
Does this mean that A::T cannot run response tests w/o
William McKee wrote:
On Fri, Mar 12, 2004 at 07:01:29PM -0800, Stas Bekman wrote:
Why do you have /usr/lib/libperl.* at all? It's a bad idea to have it in
the common path if you have more than one perl installed on the same system.
Yes, you always need to rebuild mod_perl with the new version of
On Fri, Mar 12, 2004 at 07:43:15PM -0800, Stas Bekman wrote:
It certainly can be patched not to do so. But I don't response handlers can
be useful for anything else besides mod_perl. It'd help if you'd have
explained what are you try to test. mod_cgi?
Sorry, here's the background. I've
William McKee wrote:
On Fri, Mar 12, 2004 at 07:43:15PM -0800, Stas Bekman wrote:
It certainly can be patched not to do so. But I don't response handlers can
be useful for anything else besides mod_perl. It'd help if you'd have
explained what are you try to test. mod_cgi?
Sorry, here's the
On Fri, Mar 12, 2004 at 07:44:46PM -0800, Stas Bekman wrote:
that's when you start apache/mp, right? You need to remove that library and
then rebuild mod_perl. It should now find the library under
/usr/local/lib/perl5/.../libperl.so
Yeah, sure enough I moved all the libperl.so.* out of the
On Fri, Mar 12, 2004 at 11:17:50PM -0500, William McKee wrote:
Just FYI, after moving the libperl.* out of /usr/lib and rebuilding
Apache/mp, I'm still having problems with the TestRun.pm module. I'll
try building Perl with O2 next.
Rebuilt Perl and mod_perl with -O2. But I'm still getting the
Hi Stas,
I'm running into the sticky preferences problem now as well. I decided
the quickest way to get my tests running in the Windows environment
would be to install mod_perl. The install notes suggested that the path
be c:\apache2 which means the default path of c:\program files\apache2
is no
On Sat, 13 Mar 2004, William McKee wrote:
Hi Stas,
I'm running into the sticky preferences problem now as well. I decided
the quickest way to get my tests running in the Windows environment
would be to install mod_perl. The install notes suggested that the path
be c:\apache2 which means the
On Sat, Mar 13, 2004 at 09:42:10AM -0600, Randy Kobes wrote:
I don't think being on Windows makes a difference in this
particular case - I think where it gets the info from is
C:\Perl\site\lib\Apache\BuildConfig.pm
which is generated by Apache::Build.
Thanks for the pointer Randy.
On Fri, Mar 12, 2004 at 08:06:05PM -0800, Stas Bekman wrote:
Via wrappers, of course. In which case you should write several general
purpose modules put them under project/lib (or some special lib under
project/t) and then write the wrappers (.pl for mod_cgi, .pm for mod_perl)
and put those
15 matches
Mail list logo
