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 Murphy Wayne State University
Systems Analyst II Computing & Information Technology (C&IT)
(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/
------------- End Forwarded Message -------------
Mark Murphy Wayne State University
Systems Analyst II Computing & Information Technology (C&IT)
(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/
