Re: mod_perl 1.24 testing keeps failing

2000-06-02 Thread David Mitchell

  [Thu May 25 19:34:31 2000] [error] mod_ssl: Init: Failed to generate 
temporary 5
  12 bit RSA private key

Sorry, I missed the earlier discussion on this (so I may have got
the wrong end of the stick), but I got this too when trying to build
apache 1.3.12 with perl-5.6.0 and mod_ssl 2.6.4, and I found a solution.

The problem was that mod_perl's test scripts invoke apache
with a stub config section designed to turn SSL off:

IfModule apache_ssl.c
SSLDisable


It so happens that mod_ssl tries to generate the tmp RSA key even
though it's been disabled with SSLDisable. Because there are
no SSL directives in the test conf file that define sources for randomness,
the key generation fails (and apache fails to start, and so the mod_perl
test fails).

My workaround was to add the following lines to the IfModule apache_ssl.c
session:

SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
SSLLog  logs/ssl_engine_log
SSLLogLevel info

(I suspect only the 1st of these lines is required, but this is what I
actually added that worked).


* Dave Mitchell, Operations Manager,
* Fretwell-Downing Facilities Ltd, UK.  [EMAIL PROTECTED]
* Tel: +44 114 281 6113.The usual disclaimers
*
* Standards (n). Battle insignia or tribal totems




Re: mod_perl 1.24 testing keeps failing

2000-06-02 Thread Mark Murphy


Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: mailto:[EMAIL PROTECTED]
list-unsubscribe: mailto:[EMAIL PROTECTED]
list-post: mailto:[EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
X-Authentication-Warning: mojo.covalent.net: dougm owned process doing -bs
Date: Thu, 1 Jun 2000 12:09:53 -0700 (PDT)
From: Doug MacEachern [EMAIL PROTECTED]
To: Mark Murphy [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: mod_perl 1.24 testing keeps failing
MIME-Version: 1.0
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

On Fri, 26 May 2000, Mark Murphy wrote:
 
 I have one more issue with the "make test" for mod_perl. The documentation 
 indicates that SSL doesn't like /dev/null and that SSLDisable is set. Well, 
 after changing /dev/null and making sure SSLDisable is set in the httpd.conf 
 file, I was still getting an error with mod_ssl

where did you change /dev/null ?

This was in the t/conf/httpd.conf file. Some of the logs were defined as 
/dev/null and I changed them to actual file names.

 
 [Thu May 25 19:34:31 2000] [error] mod_ssl: Init: Failed to generate 
temporary 5
 12 bit RSA private key

no idea on this one, maybe a permission problem?  strace might help:
% make start_httpd
% strace -f -s1024 -o strace.out -p `cat t/logs/httpd.pid`
% make run_tests
% make kill_httpd

there's probably an open() call in strace.out to generate the tmp key.
 

David Mitchell posted a work around for this fix. He described the problem and 
added the following lines to the IfModule mod_ssl.c section

SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
SSLLog  logs/ssl_engine_log
SSLLogLevel info

I added these lines an took out the comment for the LoadModule libssl line. The 
test worked fine, minus the module/ssi issue which should be skipped anyways.


 I had to comment out the LoadModule for libssl in the test httpd.conf file. 
Once 
 I did that I got results. During the "make test" for mod_perl I received 1 
 failure.

 modules/ssi.FAILED before any test output arrived

no cause for alarm.  the #perl ssi directive is disable when mod_perl is
built as a dso, the test should be skipped too, must be a flaw in the test
suite.


Thanks so much for your help Doug, I really appreciate the time you took to 
answer my questions.


Mark MurphyWayne State University
Systems Analyst II Computing  Information Technology (CIT)
(313) 577-4795 Voice   Academic Computing  Customer Services (ACCS)
(313) 577-8787 Fax 5425 Woodward Ave.
   Detroit,  MI.   48202

Email: [EMAIL PROTECTED]
WWW  : http://www.wayne.edu/




Re: mod_perl 1.24 testing keeps failing

2000-06-01 Thread Doug MacEachern

On Fri, 26 May 2000, Mark Murphy wrote:
 
 I have one more issue with the "make test" for mod_perl. The documentation 
 indicates that SSL doesn't like /dev/null and that SSLDisable is set. Well, 
 after changing /dev/null and making sure SSLDisable is set in the httpd.conf 
 file, I was still getting an error with mod_ssl

where did you change /dev/null ?
 
 [Thu May 25 19:34:31 2000] [error] mod_ssl: Init: Failed to generate temporary 5
 12 bit RSA private key

no idea on this one, maybe a permission problem?  strace might help:
% make start_httpd
% strace -f -s1024 -o strace.out -p `cat t/logs/httpd.pid`
% make run_tests
% make kill_httpd

there's probably an open() call in strace.out to generate the tmp key.
 
 I had to comment out the LoadModule for libssl in the test httpd.conf file. Once 
 I did that I got results. During the "make test" for mod_perl I received 1 
 failure.

 modules/ssi.FAILED before any test output arrived

no cause for alarm.  the #perl ssi directive is disable when mod_perl is
built as a dso, the test should be skipped too, must be a flaw in the test
suite.




Re: mod_perl 1.24 testing keeps failing

2000-05-26 Thread Mark Murphy


X-Authentication-Warning: mojo.covalent.net: dougm owned process doing -bs
Date: Thu, 25 May 2000 13:21:04 -0700 (PDT)
From: Doug MacEachern [EMAIL PROTECTED]
To: Mark Murphy [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: mod_perl 1.24 testing keeps failing
MIME-Version: 1.0

On Thu, 25 May 2000, Mark Murphy wrote:

 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'

those are the flags added when largefile support is enabled.

try with a fresh source tree and run:

sh Configure -des -Dcc=gcc -Ubincompat5005 -Uuselargefiles

-des will use all defaults except those you override and you don't have to
answer all those darn questions.


Thanks, everything worked out much better then before once I reconfigured perl 
and then reinstalled apache, mod_ssl, and mod_perl.

I have one more issue with the "make test" for mod_perl. The documentation 
indicates that SSL doesn't like /dev/null and that SSLDisable is set. Well, 
after changing /dev/null and making sure SSLDisable is set in the httpd.conf 
file, I was still getting an error with mod_ssl

[Thu May 25 19:34:31 2000] [error] mod_ssl: Init: Failed to generate temporary 5
12 bit RSA private key

I had to comment out the LoadModule for libssl in the test httpd.conf file. Once 
I did that I got results. During the "make test" for mod_perl I received 1 
failure.



cp t/conf/mod_perl_srm.conf t/conf/srm.conf
./apaci/load_modules.pl /usr/local/src/apache/1.3.12/apache_1.3.12/src
/usr/local/src/apache/1.3.12/apache_1.3.12/src/httpd -f `pwd`/t/conf/httpd.conf 
-X -d `pwd`/t 
httpd listening on port 8529
will write error_log to: t/logs/error_log
letting apache warm up...done
/bin/perl t/TEST 0
still waiting for server to warm up.ok
ok
modules/actions.ok   
modules/cgi.ok   
modules/constants...ok   
modules/cookie..skipped test on this platform
modules/fileok   
modules/httpdconf...ok   
modules/include.ok   
modules/log.ok   
modules/module..skipped test on this platform
modules/perlrun.ok   
modules/psections...skipped test on this platform
modules/request.skipped test on this platform
modules/src.ok   
modules/ssi.FAILED before any test output arrived
modules/stage...skipped test on this platform
modules/status..ok   
modules/symbol..skipped test on this platform
modules/uri.ok   
modules/utilok   
internal/apiok   
internal/auth...ok   
internal/croak..ok   
internal/dirmagic...ok   
internal/error..ok   
internal/headersok   
internal/hooks..ok   
internal/http-get...ok   
internal/http-post..ok   
internal/proxy..ok   
internal/redirect...ok   
internal/rwrite.ok   
internal/stackedok   
internal/table..ok   
internal/taint..ok   
Failed Test  Status Wstat Total Fail  Failed  List of failed
---
modules/ssi.t??   ??   %  ??
6 tests skipped.
httpd terminated
Failed 1/34 test scripts, 97.06% okay. 0/373 subtests failed, 100.00% okay.
*** Error code 29
make: Fatal error: Command failed for target `run_tests'




I'm happy I received a 97.06% ok, but I'm concerned that server side includes 
test failed. The

Re: mod_perl 1.24 testing keeps failing

2000-05-25 Thread Mark Murphy

Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: mailto:[EMAIL PROTECTED]
list-unsubscribe: mailto:[EMAIL PROTECTED]
list-post: mailto:[EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
X-Authentication-Warning: mojo.covalent.net: dougm owned process doing -bs
Date: Tue, 23 May 2000 20:38:26 -0700 (PDT)
From: Doug MacEachern [EMAIL PROTECTED]
To: Mark Murphy [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: mod_perl 1.24 testing keeps failing
MIME-Version: 1.0
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

On Tue, 23 May 2000, Mark Murphy wrote:

 Here is some more information I gathered from trying the "make test" under 
 mod_perl. I ran the command by hand and discovered that I'm getting a core 
dump.
 
 (gdb) backtrace
 #0  0xff1c5568 in _smalloc () from /usr/lib/libc.so.1
 #1  0xff1c55ac in malloc () from /usr/lib/libc.so.1
 #2  0xff0e2940 in Perl_savepvn ()

ah, looks like typical solaris dso problem, which mod_perl's Makefile.PL
should have warned you about and suggested solutions to pick from:

if ($]  5.006) {
phat_warn(EOF, $abort);
Your current configuration will most likely trigger core dumps,
suggestions:
   *) Do not configure mod_perl as a DSO
   *) Upgrade your Perl version to 5.6.0 or higher (w/ -Ubincompat5005)
   *) Configure Perl with -Uusemymalloc (not recommended for performance)
EOF
 }
 elsif ($bincompat) {
 phat_warn(EOF, $abort);
Your current configuration will most likely trigger core dumps,
suggestions:
   *) Do not configure mod_perl as a DSO
   *) Rebuild Perl without malloc pollution (Configure -Ubincompat5005)
EOF
}


I double checked but never received this message from mod_perl's Makefile.PL. I 
decided to install Perl 5.6.0 with the following command:

  sh Configure -Dcc=gcc -Ubincompat5005
  
I did use all the defaults and I had to include the location to my BerkeleyDB 
include and lib paths.

   -I/usr/local/BerkeleyDB.3.0/include
   -L/usr/local/BerkeleyDB.3.0/lib

Everything went fine and I then proceeded with a clean install of the mod_ssl 
2.6.4, mod_perl 1.24, and apache 1.3.12. 

I followed the Install.simple.mod_ssl file in the mod_perl source. I did alter 
the mod_perl part to include other arguments.

perl Makefile.PL USE_APACI=1 EVERYTHING=1 \
 SSL_BASE=/usr/local/src/openSSL/0.9.5a/openssl-0.9.5a \
 APACHE_PREFIX=/usr/local/apache \
 APACHE_SRC=/usr/local/src/apache/1.3.12/apache_1.3.12/src \
 DO_HTTPD=1 \ 
 APACI_ARGS=--enable-module=most,--enable-shared=max,--enable-module=ssl

I then proceeded to build apache and install it. There were no warnings or 
problems up to this point. I then tried to run apache and received the 
following error.

# ./apachectl start
Syntax error on line 213 of /usr/local/apache/conf/httpd.conf:
Cannot load /usr/local/apache/libexec/mod_negotiation.so into server: ld.so.1: 
/usr/local/apache/bin/httpd: fatal: relocation error: file 
/usr/local/apache/libexec/mod_negotiation.so: symbol __floatdisf: referenced 
symbol not found
./apachectl start: httpd could not be started
# 

I commented out the LoadModule for mod_negotiation.so and then received the 
error

# ./apachectl start
Syntax error on line 232 of /usr/local/apache/conf/httpd.conf:
Cannot load /usr/local/apache/libexec/libproxy.so into server: ld.so.1: 
/usr/local/apache/bin/httpd: fatal: relocation error: file 
/usr/local/apache/libexec/libproxy.so: symbol __floatdisf: referenced symbol 
not found
./apachectl start: httpd could not be started
# 

I did the same for libproxy module and then I was able to start the server.

# ./apachectl start
./apachectl start: httpd started
# 


Any ideas to what might be causing this??


When I do the make test in the mod_perl directory. I'm still getting a failure, 
however, its not a core dump. It seems that the error_log is telling me that 
mod_ssl has failed to Inititalize

[Thu May 25 12:06:22 2000] [error] mod_ssl: Init: Failed to generate temporary 
512 bit RSA private key

I don't know if this is because I didn't load the other two modules or not. I 
was able to load the apache ssl version and successfully connect to it with 
https://host:port. Perhaps the test is tring to write the key in the apache 
install area and not the mod_perl test area. I'll do some further experiments 
with that. 



Mark MurphyWayne State University
Systems Analyst II Computing  Information Technology (CIT)
(313) 577-4795 Voice   Academic Computing  Customer Services (ACCS)
(313) 577-8787 Fax 5425 Woodward Ave.
   Detroit,  MI.   48202

Email: [EMAIL PROTECTED]
WWW  : http://www.wayne.edu/




Re: mod_perl 1.24 testing keeps failing

2000-05-25 Thread Doug MacEachern

On Thu, 25 May 2000, Mark Murphy wrote:
 
   sh Configure -Dcc=gcc -Ubincompat5005

hmm, i've seen a similar report related to largefile support, try once
more with:

sh Configure -Dcc=gcc -Ubincompat5005 -Uuselargefiles





Re: mod_perl 1.24 testing keeps failing

2000-05-25 Thread Mark Murphy

I never mentioned this but I'm running Solaris 7 on a Ultra 10


- Begin Forwarded Message -

Date: Thu, 25 May 2000 15:28:05 -0400 (EDT)
From: Mark Murphy mark@opus
Subject: Re: mod_perl 1.24 testing keeps failing
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-MD5: L1MbykrMxzsjepplHuWHSw==

Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: mailto:[EMAIL PROTECTED]
list-unsubscribe: mailto:[EMAIL PROTECTED]
list-post: mailto:[EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
X-Authentication-Warning: mojo.covalent.net: dougm owned process doing -bs
Date: Tue, 23 May 2000 20:38:26 -0700 (PDT)
From: Doug MacEachern [EMAIL PROTECTED]
To: Mark Murphy [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: mod_perl 1.24 testing keeps failing
MIME-Version: 1.0
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

On Tue, 23 May 2000, Mark Murphy wrote:

 Here is some more information I gathered from trying the "make test" under 
 mod_perl. I ran the command by hand and discovered that I'm getting a core 
dump.
 
 (gdb) backtrace
 #0  0xff1c5568 in _smalloc () from /usr/lib/libc.so.1
 #1  0xff1c55ac in malloc () from /usr/lib/libc.so.1
 #2  0xff0e2940 in Perl_savepvn ()

ah, looks like typical solaris dso problem, which mod_perl's Makefile.PL
should have warned you about and suggested solutions to pick from:

if ($]  5.006) {
phat_warn(EOF, $abort);
Your current configuration will most likely trigger core dumps,
suggestions:
   *) Do not configure mod_perl as a DSO
   *) Upgrade your Perl version to 5.6.0 or higher (w/ -Ubincompat5005)
   *) Configure Perl with -Uusemymalloc (not recommended for performance)
EOF
 }
 elsif ($bincompat) {
 phat_warn(EOF, $abort);
Your current configuration will most likely trigger core dumps,
suggestions:
   *) Do not configure mod_perl as a DSO
   *) Rebuild Perl without malloc pollution (Configure -Ubincompat5005)
EOF
}


I double checked but never received this message from mod_perl's Makefile.PL. I 
decided to install Perl 5.6.0 with the following command:

  sh Configure -Dcc=gcc -Ubincompat5005
  
I did use all the defaults and I had to include the location to my BerkeleyDB 
include and lib paths.

   -I/usr/local/BerkeleyDB.3.0/include
   -L/usr/local/BerkeleyDB.3.0/lib

Everything went fine and I then proceeded with a clean install of the mod_ssl 
2.6.4, mod_perl 1.24, and apache 1.3.12. 

I followed the Install.simple.mod_ssl file in the mod_perl source. I did alter 
the mod_perl part to include other arguments.

perl Makefile.PL USE_APACI=1 EVERYTHING=1 \
 SSL_BASE=/usr/local/src/openSSL/0.9.5a/openssl-0.9.5a \
 APACHE_PREFIX=/usr/local/apache \
 APACHE_SRC=/usr/local/src/apache/1.3.12/apache_1.3.12/src \
 DO_HTTPD=1 \ 
 APACI_ARGS=--enable-module=most,--enable-shared=max,--enable-module=ssl

I then proceeded to build apache and install it. There were no warnings or 
problems up to this point. I then tried to run apache and received the 
following error.

# ./apachectl start
Syntax error on line 213 of /usr/local/apache/conf/httpd.conf:
Cannot load /usr/local/apache/libexec/mod_negotiation.so into server: ld.so.1: 
/usr/local/apache/bin/httpd: fatal: relocation error: file 
/usr/local/apache/libexec/mod_negotiation.so: symbol __floatdisf: referenced 
symbol not found
./apachectl start: httpd could not be started
# 

I commented out the LoadModule for mod_negotiation.so and then received the 
error

# ./apachectl start
Syntax error on line 232 of /usr/local/apache/conf/httpd.conf:
Cannot load /usr/local/apache/libexec/libproxy.so into server: ld.so.1: 
/usr/local/apache/bin/httpd: fatal: relocation error: file 
/usr/local/apache/libexec/libproxy.so: symbol __floatdisf: referenced symbol 
not found
./apachectl start: httpd could not be started
# 

I did the same for libproxy module and then I was able to start the server.

# ./apachectl start
./apachectl start: httpd started
# 


Any ideas to what might be causing this??


When I do the make test in the mod_perl directory. I'm still getting a failure, 
however, its not a core dump. It seems that the error_log is telling me that 
mod_ssl has failed to Inititalize

[Thu May 25 12:06:22 2000] [error] mod_ssl: Init: Failed to generate temporary 
512 bit RSA private key

I don't know if this is because I didn't load the other two modules or not. I 
was able to load the apache ssl version and successfully connect to it with 
https://host:port. Perhaps the test is tring to write the key in the apache 
install area and not the mod_perl test area. I'll do some further experiments 
with that. 



Mark MurphyWayne State University
Systems Analyst II Computing  Information Technology (CIT)
(313) 577-4795 Voice   Academic Computing  Customer Services (ACCS)
(313) 577-8787 Fax 5425 Woodward Ave.
   Detroit,  MI.   48202

Email: [EMAIL PROTECTED]
WWW  : http://www.wayne.edu/


---

Re: mod_perl 1.24 testing keeps failing

2000-05-25 Thread Mark Murphy


Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: mailto:[EMAIL PROTECTED]
list-unsubscribe: mailto:[EMAIL PROTECTED]
list-post: mailto:[EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
X-Authentication-Warning: mojo.covalent.net: dougm owned process doing -bs
Date: Thu, 25 May 2000 12:57:33 -0700 (PDT)
From: Doug MacEachern [EMAIL PROTECTED]
To: Mark Murphy [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: mod_perl 1.24 testing keeps failing
MIME-Version: 1.0
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

On Thu, 25 May 2000, Mark Murphy wrote:
 
   sh Configure -Dcc=gcc -Ubincompat5005

hmm, i've seen a similar report related to largefile support, try once
more with:

sh Configure -Dcc=gcc -Ubincompat5005 -Uuselargefiles



I believe it already did by default. Here is the output from my perl -V

==
bash(mark:opus)1201% perl -V
Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
  Platform:
osname=solaris, osvers=2.7, archname=sun4-solaris
uname='sunos opus 5.7 generic_106541-10 sun4u sparc sunw,ultra-5_10 '
config_args='-Dcc=gcc -Ubincompat5005'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef 
usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define 
use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
  Compiler:
cc='gcc', optimize='-O', gccversion=2.95.2 19991024 (release)
cppflags='-fno-strict-aliasing -I/usr/local/include 
-I/usr/local/BerkeleyDB.3.0/include'
ccflags ='-fno-strict-aliasing -I/usr/local/include 
-I/usr/local/BerkeleyDB.3.0/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'
stdchar='char', d_stdstdio=define, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', 
lseeksize=8
alignbytes=8, usemymalloc=y, prototype=define
  Linker and Libraries:
ld='gcc', ldflags ='-L/usr/local/lib -L/usr/local/BerkeleyDB.3.0/lib '
libpth=/usr/local/lib /lib /usr/lib /usr/ccs/lib 
/usr/local/BerkeleyDB.3.0/lib
libs=-lsocket -lnsl -ldb -ldl -lm -lc -lcrypt -lsec
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib 
-L/usr/local/BerkeleyDB.3.0/lib'


Characteristics of this binary (from libperl): 
  Compile-time options: USE_LARGE_FILES
  Built under solaris
  Compiled at May 24 2000 12:16:14
  @INC:
/usr/local/lib/perl5/5.6.0/sun4-solaris
/usr/local/lib/perl5/5.6.0
/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris
/usr/local/lib/perl5/site_perl/5.6.0
/usr/local/lib/perl5/site_perl
.
==

I did notice that it also set the -D_FILE_OFFSET_BITS=64, however, the default 
in the perl config was set to no
 
 
 
==
Perl can be built to understand large files (files larger than 2 gigabytes)
on some systems.  To do so, Configure can be run with -Duselargefiles.

If this doesn't make any sense to you, just accept the default 'y'.
Try to understand large files, if available? [y] 
Your platform has some specific hints for large file builds, using them...
 
Rechecking to see how big your file offsets are...
Your file offsets are now 8 bytes long.
Rechecking the size of fpos_t... 8 bytes.

Perl can be built to take advantage of 64-bit integer types
on some systems.  To do so, Configure can be run with -Duse64bitint.
Choosing this option will most probably introduce binary incompatibilities.

If this doesn't make any sense to you, just accept the default 'n'.
Try to use 64-bit integers, if available? [n] 

You may also choose to try maximal 64-bitness.  It means using as much
64-bitness as possible on the platform.  This in turn means even more
binary incompatibilities.  On the other hand, your platform may not
have any more 64-bitness available than what you already have chosen.

If this doesn't make any sense to you, just accept the default 'n'.
Try to use maximal 64-bit support, if available? [n] 
==

Should I still reconfigure perl with the -Uuselargefiles parameter? Is the 
-D_FILE_OFFSET_BITS=64 set by the -Duse64bitint? If so, then the script didn't 
take the default [n].


Mark MurphyWayne State University
Systems Analyst II Computing  Information Technology (CIT)
(313) 577-4795 Voice   Academic Computing  Customer Services (ACCS)
(313) 577-8787 Fax 5425 Woodward Ave.
   Detroit,  MI.   48202

Email: [EMAIL PROTECTED]
WWW  : http://www.wayne.edu/




Re: mod_perl 1.24 testing keeps failing

2000-05-25 Thread Doug MacEachern

On Thu, 25 May 2000, Mark Murphy wrote:

 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'

those are the flags added when largefile support is enabled.

try with a fresh source tree and run:

sh Configure -des -Dcc=gcc -Ubincompat5005 -Uuselargefiles

-des will use all defaults except those you override and you don't have to
answer all those darn questions.




mod_perl 1.24 testing keeps failing

2000-05-23 Thread Mark Murphy


I'm having a problem with the make test in mod_perl 1.24. It doesn't seem to be 
configured correctly. Here are the steps I've taken so far.


mod_perl 1.24
-
1. perl Makefile.PL APACHE_SRC=/usr/local/src/apache/1.3.12/apache_1.3.12/src 
DO_HTTPD=1 USE_APACI=1 PREP_HTTPD=1 EVERYTHING=1

mod_ssl 2.6.4-1.3.12

2. ./configure --with-apache=/usr/local/src/apache/1.3.12/apache_1.3.12

Apache 1.3.12
-
3. SSL_BASE=/usr/local/src/openSSL/0.9.5a/openssl-0.9.5a \
 RSA_BASE=/usr/local/src/rsaref/2.0/rsaref20/sun \
 ./configure \
 --enable-module=most \
 --enable-shared=max \
 --prefix=/usr/local/apache \
 --enable-module=ssl \
 --activate-module=src/modules/perl/libperl.a \
 --enable-shared=perl
 
4. make
5. make certificate TYPE=test
6. su
7. make install

mod_perl 1.24
-
8. make
9. make test


It seems that the t/conf/httpd.conf file is not created properly. I tried hand 
editing the file and removing the =pod and related lines from this file, 
however, when I run the test I get the following...


bash(mark:opus)1503% make test
cp t/conf/mod_perl_srm.conf t/conf/srm.conf
/usr/local/src/apache/1.3.12/apache_1.3.12/src/httpd -f `pwd`/t/conf/httpd.conf 
-X -d `pwd`/t 
httpd listening on port 8529
will write error_log to: t/logs/error_log
letting apache warm up...Syntax error on line 5 of 
/usr/local/src/perl-modules/mod_perl/1.24/mod_perl-1.24/t/conf/httpd.conf:
Invalid command 'PerlTaintCheck', perhaps mis-spelled or defined by a module not 
included in the server configuration
done
/usr/local/bin/perl t/TEST 0
still waiting for server to warm up...not ok
server failed to start! (please examine t/logs/error_log) at t/TEST line 95.
*** Error code 9
make: Fatal error: Command failed for target `run_tests'


There is nothing in the t/logs/error_log. Any ideas to what is wrong here? does 
the make test under mod_perl even work?? Should I skip this step all together? 
ANy help would be greatly appreciated. Thanks



Mark MurphyWayne State University
Systems Analyst II Computing  Information Technology (CIT)
(313) 577-4795 Voice   Academic Computing  Customer Services (ACCS)
(313) 577-8787 Fax 5425 Woodward Ave.
   Detroit,  MI.   48202

Email: [EMAIL PROTECTED]
WWW  : http://www.wayne.edu/






Re: mod_perl 1.24 testing keeps failing

2000-05-23 Thread Doug MacEachern

On Tue, 23 May 2000, Mark Murphy wrote:

 
 I'm having a problem with the make test in mod_perl 1.24. It doesn't seem to be 
 configured correctly. Here are the steps I've taken so far.

 Invalid command 'PerlTaintCheck', perhaps mis-spelled or defined by a module not 

this indicates that mod_perl is not configured with your server.
try building using the steps in INSTALL.simple.mod_ssl





Re: mod_perl 1.24 testing keeps failing

2000-05-23 Thread Doug MacEachern

On Tue, 23 May 2000, Mark Murphy wrote:

 Here is some more information I gathered from trying the "make test" under 
 mod_perl. I ran the command by hand and discovered that I'm getting a core dump.
 
 (gdb) backtrace
 #0  0xff1c5568 in _smalloc () from /usr/lib/libc.so.1
 #1  0xff1c55ac in malloc () from /usr/lib/libc.so.1
 #2  0xff0e2940 in Perl_savepvn ()

ah, looks like typical solaris dso problem, which mod_perl's Makefile.PL
should have warned you about and suggested solutions to pick from:

if ($]  5.006) {
phat_warn(EOF, $abort);
Your current configuration will most likely trigger core dumps,
suggestions:
   *) Do not configure mod_perl as a DSO
   *) Upgrade your Perl version to 5.6.0 or higher (w/ -Ubincompat5005)
   *) Configure Perl with -Uusemymalloc (not recommended for performance)
EOF
 }
 elsif ($bincompat) {
 phat_warn(EOF, $abort);
Your current configuration will most likely trigger core dumps,
suggestions:
   *) Do not configure mod_perl as a DSO
   *) Rebuild Perl without malloc pollution (Configure -Ubincompat5005)
EOF
}