RE: can't fine ModuleConfig.c.

2002-08-15 Thread Goehring, Chuck Mr., RCI - San Diego


Thanks.  You are the hero of us lonely Windows Apache users.

Chuck


-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 11:10 PM
To: Goehring, Chuck Mr., RCI - San Diego
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: can't fine ModuleConfig.c.


On Mon, 12 Aug 2002, Goehring, Chuck Mr., RCI - San Diego wrote:

 Randy,
 
 I'm using Perl 5.6.0 for this. Should I be using 5.8.0?  Does
 that affect ModuleConfig.c?
 
 Having problems running things with the version I put out last
 week.  It complains about the dumbest things and is overly
 strict.
 
 Thanks
 Chuck

I'm not sure if this will help, but an error you had in an
earlier message for 'perl Makefile.PL' indicated you didn't have
touch() on your system (which is typical for Win32). You might
want to try the attached patch to Makefile.PL, which uses a perl
command for touch().

-- 
best regards,
randy



RE: can't fine ModuleConfig.c.

2002-08-14 Thread Randy Kobes

On Mon, 12 Aug 2002, Goehring, Chuck Mr., RCI - San Diego wrote:

 Randy,
 
 I'm using Perl 5.6.0 for this. Should I be using 5.8.0?  Does
 that affect ModuleConfig.c?
 
 Having problems running things with the version I put out last
 week.  It complains about the dumbest things and is overly
 strict.
 
 Thanks
 Chuck

I'm not sure if this will help, but an error you had in an
earlier message for 'perl Makefile.PL' indicated you didn't have
touch() on your system (which is typical for Win32). You might
want to try the attached patch to Makefile.PL, which uses a perl
command for touch().

-- 
best regards,
randy


Index: Makefile.PL
===
RCS file: /home/cvspublic/modperl/Makefile.PL,v
retrieving revision 1.204
diff -u -r1.204 Makefile.PL
--- Makefile.PL 19 Jun 2002 16:31:52 -  1.204
+++ Makefile.PL 15 Aug 2002 05:48:46 -
 -1600,7 +1600,10 
my $to = '$(INST_ARCHLIB)/' . auto/Apache/include/$_;
unless ($self-{PM}-{$from}) {
$self-{PM}-{$from} = $to;
-   system $Config{touch} $from;
+my args = ($Config{perlpath}, '-MExtUtils::Command', '-e', 'touch', 
+$from);
+system(args) == 0
+  or die system args failed: $?;
+#system $Config{touch} $from;
}
 }
 



RE: can't fine ModuleConfig.c.

2002-08-13 Thread Randy Kobes

On Mon, 12 Aug 2002, Goehring, Chuck Mr., RCI - San Diego wrote:

 Randy,
 
 I'm using Perl 5.6.0 for this. Should I be using 5.8.0?  Does
 that affect ModuleConfig.c?

There may be some advantages to using 5.8.0 with mod_perl-2 on
Win32, but 5.6.1 should be fine with mod_perl-1.

 
 Having problems running things with the version I put out last
 week.  It complains about the dumbest things and is overly
 strict.
 
 Thanks
 Chuck

What sort of things appear in the error log? Is it possible to
give a short example which exhibits the problem?

-- 
best regards,
randy




RE: can't fine ModuleConfig.c.

2002-08-13 Thread Goehring, Chuck Mr., RCI - San Diego

Randy,

My server barfed and I had to re-format.  Do you think I ought to go with Apache 2?  I 
need to get to full time ssl to meet the security requirements anyway.  I was planning 
to do this when I go hit with the need to close that vulnerability in Apache.  Is the 
2.0 ready for prime time on Win 2000?  I really would like to get off this pathetic 
single-threaded arrangement with Apache 1.x.

Thanks
Chuck


-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 13, 2002 9:03 AM
To: Goehring, Chuck Mr., RCI - San Diego
Cc: mod perl list (E-mail)
Subject: RE: can't fine ModuleConfig.c.


On Mon, 12 Aug 2002, Goehring, Chuck Mr., RCI - San Diego wrote:

 Randy,
 
 I'm using Perl 5.6.0 for this. Should I be using 5.8.0?  Does
 that affect ModuleConfig.c?

There may be some advantages to using 5.8.0 with mod_perl-2 on
Win32, but 5.6.1 should be fine with mod_perl-1.

 
 Having problems running things with the version I put out last
 week.  It complains about the dumbest things and is overly
 strict.
 
 Thanks
 Chuck

What sort of things appear in the error log? Is it possible to
give a short example which exhibits the problem?

-- 
best regards,
randy




RE: can't fine ModuleConfig.c.

2002-08-12 Thread Goehring, Chuck Mr., RCI - San Diego

Randy,

I'm using Perl 5.6.0 for this. Should I be using 5.8.0?  Does that affect 
ModuleConfig.c?

Having problems running things with the version I put out last week.  It complains 
about the dumbest things and is overly strict.

Thanks
Chuck


-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 06, 2002 12:34 PM
To: Goehring, Chuck Mr., RCI - San Diego
Cc: mod perl list (E-mail)
Subject: RE: can't fine ModuleConfig.c.


On Sun, 4 Aug 2002, Goehring, Chuck Mr., RCI - San Diego wrote:

 Randy,
 
 Got things working - had to get that thing into production
 before the security folks took us out of the dns.
 
 Failed modperl's test because the test required Process.pm
 which in turn required the entire libwin32 (which died during
 compile).  On the modperl side, I deleted ModuleConfig.c fom
 the project and it compiled.

Are you using a recent ActivePerl? The libwin32 suite
should be there, if you are ...

 
 Did:
perl Makefile.PL
nmake install
Built .so file using VC++ IDE.
nmake test (died because of Process.pm)
nmake install
 
 Did not modify any make or provide any options to Makefile.PL
 
 
 As dangerous as this seams, it did run and passed minimal
 testing.  Have had no reports of problems from the users.  It
 isn't doing e-commerce or the like.
 
 Something is up with ModuleConfig.c though.  I don't know what
 that file does.  We use mod_perl just to speed up cgis so maybe
 it isn't needed for my purposes.

I'll try to look into what's up with ModuleConfig.c ... 

best regards,
randy





RE: can't fine ModuleConfig.c.

2002-08-04 Thread Goehring, Chuck Mr., RCI - San Diego

Randy,

Got things working - had to get that thing into production before the security folks 
took us out of the dns.

Failed modperl's test because the test required Process.pm which in turn required the 
entire libwin32 (which died during compile).  On the modperl side, I deleted 
ModuleConfig.c fom the project and it compiled.  

Did:
   perl Makefile.PL
   nmake install
   Built .so file using VC++ IDE.
   nmake test (died because of Process.pm)
   nmake install

Did not modify any make or provide any options to Makefile.PL


As dangerous as this seams, it did run and passed minimal testing.  Have had no 
reports of problems from the users.  It isn't doing e-commerce or the like.

Something is up with ModuleConfig.c though.  I don't know what that file does.  We use 
mod_perl just to speed up cgis so maybe it isn't needed for my purposes.

Thanks
Chuck




-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 02, 2002 6:06 PM
To: Goehring, Chuck Mr., RCI - San Diego
Subject: Re: can't fine ModuleConfig.c.


On Thu, 1 Aug 2002, Goehring, Chuck Mr., RCI - San Diego wrote:

 
 
 Please disregard other messages.  This is the one I'm stuck on.  
 Everything builds except the ModuleConfig.c.
 
 

I didn't include the list, as I'm not sure about this ...
Did you build things as
   perl Makefile.PL APACHE_SRC=\Apache
and, if so, were there any errors? At least one person noticed
a missing touch() command, which you can do by hand, and then
the rest of the build went OK ...

-- 
best regards,
randy kobes