Return-Path: Delivered-To: apmail-modperl-cvs-archive@apache.org Received: (qmail 93045 invoked by uid 500); 25 Apr 2001 05:26:28 -0000 Mailing-List: contact modperl-cvs-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@perl.apache.org Delivered-To: mailing list modperl-cvs@apache.org Received: (qmail 93030 invoked by uid 500); 25 Apr 2001 05:26:28 -0000 Delivered-To: apmail-modperl-2.0-cvs@apache.org Date: 25 Apr 2001 05:26:27 -0000 Message-ID: <20010425052627.93024.qmail@apache.org> From: sbekman@apache.org To: modperl-2.0-cvs@apache.org Subject: cvs commit: modperl-2.0/pod modperl_dev.pod sbekman 01/04/24 22:26:27 Modified: pod modperl_dev.pod Log: documenting my latest build experience based on Doug's helpful notes: * always run 'make testclean' in httpd-2.0 source after cvs up * notes to debug 'make test' * raise the priority of using util/config.pl versus manual approach Revision Changes Path 1.19 +31 -8 modperl-2.0/pod/modperl_dev.pod Index: modperl_dev.pod =================================================================== RCS file: /home/cvs/modperl-2.0/pod/modperl_dev.pod,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- modperl_dev.pod 2001/04/25 02:44:34 1.18 +++ modperl_dev.pod 2001/04/25 05:26:27 1.19 @@ -22,6 +22,16 @@ --with-mpm=threaded --enable-so % make && make install +Once extracted, whenever you want to sync with the latest httpd-2.0 +version and rebuild, run: + + % cd httpd-2.0 + % cvs up + % make testclean && ./buildconf + % ./configure --prefix=$HOME/apache-2.0 \ + --with-mpm=threaded --enable-so + % make && make install + For bleeding edge Perl: % rsync -auvz rsync://ftp.linux.activestate.com/perl-current/ perl-current @@ -118,8 +128,6 @@ =back - - Options can also be specified in the file C. Command line options override those from C and those from MP_OPTIONS_FILE. @@ -151,9 +159,12 @@ =head1 Support Discussion of mod_perl-2.0 currently takes place on the -dev@perl.apache.org list. -Any problems/questions should be report to that list, be sure to -include: +dev@perl.apache.org list. Any problems/questions should be report to +that list, be sure to include the output of: + + % perl util/config.pl + +which generates the output from: =over 4 @@ -165,11 +176,23 @@ =back -hint: +You can also use I. - % perl util/config.pl +=head1 'make test' Debug + +mod_perl-2.0 provides built in 'make test' debug facility. So in case +you get a core dump during make test, or just for fun, run in one shell: + + % t/TEST -debug + +in another shell: + + % t/TEST -run + +then the I<-debug> shell will have a (gdb) prompt, type 'where' for +stacktrace. + -will generate this requested information. =head1 mod_perl configuration directives