cvs commit: modperl-docs/src/docs/1.0/guide install.pod
stas2004/08/06 16:34:34 Modified:src/docs/1.0/guide install.pod Log: rewrite the section that talks about using Perl w/ -Dusemymalloc for mod_perl DSO Revision ChangesPath 1.26 +37 -20modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.25 retrieving revision 1.26 diff -u -u -r1.25 -r1.26 --- install.pod 18 Mar 2004 20:23:01 - 1.25 +++ install.pod 6 Aug 2004 23:34:34 - 1.26 @@ -1050,40 +1050,57 @@ without having to mangle the Apache source tree for mod_perl. It also gives you the freedom to add third-party modules. -=head2 When DSO can be Used -If you want to build Cmod_perl as DSO you must make sure that Perl -was built with system's native malloc(). If Perl was built with its -own malloc() and C-Dbincompat5005, it pollutes the main Chttpd -program with Ifree and Imalloc symbols. When Chttpd restarts -(happens at startup too), any references in the main program to -Ifree and Imalloc become invalid, and this causes memory leaks and -segfaults. -Notice that mod_perl's build system warns about this problem. -With Perl 5.6.0+ this pollution can be prevented with -C-Ubincompat5005. or C-Uusemymalloc for any version of Perl, but -there's a chance that might hurt performance depending on platform, so -C-Ubincompat5005 is likely a better choice. -If you get the following reports with Perl version 5.6.0+: + + +=head2 When DSO can be Used + +Perl versions prior to 5.6.0, built with C-Dusemymalloc, and +versions 5.6.0 and higher, built with C-Dusemymalloc and +C-Dbincompat5005, pollutes the main Chttpd program with Ifree +and Imalloc symbols. When Chttpd restarts (happens at startup +too), any references in the main program to Ifree and Imalloc +become invalid, and this causes memory leaks and segfaults. + +First check which malloc, your Perl was built with, by running: % perl -V:usemymalloc + +If you get: + + usemymalloc='n'; + +which means that Perl is using the system malloc, mod_perl will work +fine as DSO. Continue reading this section if it's not the case. + +If you get: + usemymalloc='y'; + +that means that Perl is using its own malloc. If you are running Perl +older than 5.6.0, you must rebuild Perl with C-Uusemymalloc. If you +are running Perl 5.6.0 and higher, you must make sure that you have +the binary compatibility with Perl 5.005 turned off. To check, run: + % perl -V:bincompat5005 + +If you get: + bincompat5005='define'; -rebuild Perl with C-Ubincompat5005. +then you must rebuild Perl with C-Ubincompat5005. You can continue +using Perl's malloc if that's a better choice for your OS. + +Notice that mod_perl's build system warns about this problem. + +If you needed to rebuild Perl don't forget to rebuild mod_perl too. -For Perl versions pre-5.6.x, if you get: - % perl -V:usemymalloc - usemymalloc='y'; -rebuild Perl with C-Uusemymalloc. -Now rebuild mod_perl. =head2 Build mod_perl as a DSO inside the Apache Source Tree via APACI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide install.pod
theory 2004/08/06 16:50:06 Modified:src/docs/1.0/guide install.pod Log: Tweaking for grammar, flow, anal retentive detail, etc. :-) Revision ChangesPath 1.27 +17 -23modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- install.pod 6 Aug 2004 23:34:34 - 1.26 +++ install.pod 6 Aug 2004 23:50:05 - 1.27 @@ -1050,22 +1050,17 @@ without having to mangle the Apache source tree for mod_perl. It also gives you the freedom to add third-party modules. - - - - - - =head2 When DSO can be Used Perl versions prior to 5.6.0, built with C-Dusemymalloc, and -versions 5.6.0 and higher, built with C-Dusemymalloc and -C-Dbincompat5005, pollutes the main Chttpd program with Ifree -and Imalloc symbols. When Chttpd restarts (happens at startup +versions 5.6.0 and newer, built with C-Dusemymalloc and +C-Dbincompat5005, pollute the main Chttpd program with Ifree +and Imalloc symbols. When Chttpd restarts (happens at startup too), any references in the main program to Ifree and Imalloc become invalid, and this causes memory leaks and segfaults. -First check which malloc, your Perl was built with, by running: +To determine if you can use a DSO mod_perl with your version of +Perl, first find out which malloc your Perl was built with by running: % perl -V:usemymalloc @@ -1073,17 +1068,18 @@ usemymalloc='n'; -which means that Perl is using the system malloc, mod_perl will work -fine as DSO. Continue reading this section if it's not the case. +then it means that Perl is using the system malloc, so mod_perl will +work fine as DSO. If you get: usemymalloc='y'; -that means that Perl is using its own malloc. If you are running Perl -older than 5.6.0, you must rebuild Perl with C-Uusemymalloc. If you -are running Perl 5.6.0 and higher, you must make sure that you have -the binary compatibility with Perl 5.005 turned off. To check, run: +it means that Perl is using its own malloc. If you are running Perl +older than 5.6.0, you Imust rebuild Perl with C-Uusemymalloc in +order to use it with a DSO mod_perl. If you are running Perl 5.6.0 or +newer, you must either rebuild Perl with C-Uusemymalloc, or make sure +that binary compatibility with Perl 5.005 turned off. To find out, run: % perl -V:bincompat5005 @@ -1091,16 +1087,14 @@ bincompat5005='define'; -then you must rebuild Perl with C-Ubincompat5005. You can continue -using Perl's malloc if that's a better choice for your OS. +then you Imust either rebuild Perl with C-Ubincompat5005 or with +C-Uusemymalloc to use it with a DSO mod_perl. We recommend that you +rebuild Perl with C-Ubincompat5005 if Perl's malloc is a better choice +for your OS. -Notice that mod_perl's build system warns about this problem. +Note that mod_perl's build system issues a warning about this problem. If you needed to rebuild Perl don't forget to rebuild mod_perl too. - - - - =head2 Build mod_perl as a DSO inside the Apache Source Tree via APACI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: modperl-docs/src/docs/1.0/guide install.pod
[EMAIL PROTECTED] wrote: theory 2004/08/06 16:50:06 Modified:src/docs/1.0/guide install.pod Log: Tweaking for grammar, flow, anal retentive detail, etc. :-) Thanks for the edits, David :) - - - - - - =head2 When DSO can be Used well, actually starting with mp2 docs, I add quite a few new lines between sections, so it's easier to read long pod files. Visual white space helps a lot to edit and manipulate the docs. so I started to add those to older docs, when I work on those... [...] -that means that Perl is using its own malloc. If you are running Perl -older than 5.6.0, you must rebuild Perl with C-Uusemymalloc. If you -are running Perl 5.6.0 and higher, you must make sure that you have -the binary compatibility with Perl 5.005 turned off. To check, run: +it means that Perl is using its own malloc. If you are running Perl +older than 5.6.0, you Imust rebuild Perl with C-Uusemymalloc in If you want to stress something better use bold: Bmust ;) -- __ Stas BekmanJAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide --- http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: modperl-docs/src/docs/1.0/guide install.pod
On Aug 6, 2004, at 5:12 PM, Stas Bekman wrote: well, actually starting with mp2 docs, I add quite a few new lines between sections, so it's easier to read long pod files. Visual white space helps a lot to edit and manipulate the docs. so I started to add those to older docs, when I work on those... As you wish. I myself stick this sort of divider in a lot my docs: =cut =head2 When to use DSO If you want to stress something better use bold: Bmust ;) Yes, I know that. Either is fine with me. Cheers, David smime.p7s Description: S/MIME cryptographic signature
cvs commit: modperl-docs/src/docs/1.0/guide install.pod
stas2004/01/23 13:10:52 Modified:src/docs/1.0/guide install.pod Log: SSL_BASE=/usr/local/ssl doesn't work for some users with non-standard install of openssl. point them to the mod_ssl documentation in this case. Revision ChangesPath 1.23 +7 -0 modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.22 retrieving revision 1.23 diff -u -u -r1.22 -r1.23 --- install.pod 18 Nov 2003 16:52:53 - 1.22 +++ install.pod 23 Jan 2004 21:10:52 - 1.23 @@ -1259,6 +1259,13 @@ Note: Do not forget that if you use Ccsh or Ctcsh you may need to put all the arguments to `perl Makefile.PL' on a single command line. +Note: If when specifying CSSL_BASE=/usr/local/ssl Apache's configure +doesn't find the ssl libraries, please refer to the mod_ssl +documentation to figure out what CSSL_BASE argument it expects +(usually needed when ssl is not installed in the standard places). +This topic is out of scope of this document. For some setups using +CSSL_BASE=/usr/local does the trick. + Build, test and install: % make make test make install - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide install.pod
stas2003/11/18 08:52:54 Modified:src/docs/1.0/guide install.pod Log: missing src/ subdir in 'make certificate' of apache-ssl build Submitted by: Bob Wilkinson [EMAIL PROTECTED] Revision ChangesPath 1.22 +2 -2 modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.21 retrieving revision 1.22 diff -u -u -r1.21 -r1.22 --- install.pod 9 Feb 2003 02:05:19 - 1.21 +++ install.pod 18 Nov 2003 16:52:53 - 1.22 @@ -1394,7 +1394,7 @@ =item 1 - % make certificate + % make certificate with whatever option is suitable to your configuration. @@ -1454,7 +1454,7 @@ Build, test and install: % make make test make install - % cd ../apache_1.3.xx + % cd ../apache_1.3.xx/src % make certificate % make install - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide install.pod
stas2003/01/29 14:27:38 Modified:src/docs/1.0/guide install.pod Log: adding two notes to docs/1.0/guide/install.pod explaing that libperl.a (and libphp4.a) are not expected to be in the src/modules dir during ./configure Submitted by: Thomas Klausner [EMAIL PROTECTED] Reviewed by: stas Revision ChangesPath 1.19 +6 -0 modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- install.pod 31 Dec 2002 19:24:25 - 1.18 +++ install.pod 29 Jan 2003 22:27:38 - 1.19 @@ -1036,6 +1036,9 @@ C--prefix=/usr/share/apache the Apache directory tree will be installed in I/usr/share/apache. +Note that the files activated by C--activate-module do not exist at +this time. They will be generated during compilation. + The last three steps build, test and install the Apache-side of the mod_perl enabled server. Presumably your new server includes third-party components, otherwise you probably won't choose this @@ -1555,6 +1558,9 @@ --enable-module=stats \ --enable-module=rewrite % make + +Note: Clibperl.a and Clibphp4.a do not exist at this time. They +will be generated during compilation. =item 1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide install.pod
stas2003/01/29 15:44:15 Modified:src/docs/1.0/guide install.pod Log: use italic for files Revision ChangesPath 1.20 +1 -1 modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- install.pod 29 Jan 2003 22:27:38 - 1.19 +++ install.pod 29 Jan 2003 23:44:15 - 1.20 @@ -1559,7 +1559,7 @@ --enable-module=rewrite % make -Note: Clibperl.a and Clibphp4.a do not exist at this time. They +Note: Ilibperl.a and Ilibphp4.a do not exist at this time. They will be generated during compilation. =item 1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide install.pod Changes.pod
stas02/03/25 17:42:58 Modified:src/docs/1.0/guide install.pod Changes.pod Log: a few minor fixes in the download url and a typo Obtained from: Per Einar Ellefsen [EMAIL PROTECTED] Reviewed by: stas Revision ChangesPath 1.7 +2 -2 modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- install.pod 20 Mar 2002 17:43:04 - 1.6 +++ install.pod 26 Mar 2002 01:42:58 - 1.7 @@ -14,7 +14,7 @@ standard flavor of Unix OS. % cd /usr/src - % lwp-download http://www.apache.org/dist/apache_x.x.x.tar.gz + % lwp-download http://www.apache.org/dist/httpd/apache_x.x.x.tar.gz % lwp-download http://perl.apache.org/dist/mod_perl-x.xx.tar.gz % tar xzvf apache_x.x.x.tar.gz % tar xzvf mod_perl-x.xx.tar.gz @@ -164,7 +164,7 @@ or by explicitly adding Cmod_so via: - ./configure --enable-module=so. + ./configure --enable-module=so =item APache eXtenSion (APXS) support tool 1.4 +1 -1 modperl-docs/src/docs/1.0/guide/Changes.pod Index: Changes.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/Changes.pod,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Changes.pod 25 Mar 2002 15:41:50 - 1.3 +++ Changes.pod 26 Mar 2002 01:42:58 - 1.4 @@ -53,7 +53,7 @@ o remove qw() or variables list in guide::perl (Tim Noll [EMAIL PROTECTED]) - + o install: (Per Einar Ellefsen [EMAIL PROTECTED]) =head1 Nov 15 2001 ver 1.31 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide install.pod
stas02/02/04 18:51:36
Modified:src/docs/1.0/guide install.pod
Log:
- more links fixes
Revision ChangesPath
1.3 +9 -14 modperl-docs/src/docs/1.0/guide/install.pod
Index: install.pod
===
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- install.pod 4 Feb 2002 13:50:25 - 1.2
+++ install.pod 5 Feb 2002 02:51:36 - 1.3
@@ -978,7 +978,7 @@
-=head1 Installation Scenarios for Standalone mod_perl
+=head1 Installation Scenarios for Standalone mod_perl
There are various ways available to build Apache with the new hybrid
build environment (using CUSE_APACI=1):
@@ -2156,19 +2156,14 @@
Some people have reported that even when the server responds
positively to the LHow can I tell whether mod_perl is
-running|install/How_can_I_tell_whether_mod_perl_ tests, the mod_perl
-API will not function properly. You may want to run the following script
-to verify the availability of the mod_perl API.
-
- use strict;
- my $r = shift;
- $r-send_http_header('text/html');
- $r-print(It worked!!!\n);
-
-
-
-
-
+running|install/How_can_I_tell_whether_mod_perl_is_running_ tests,
+the mod_perl API will not function properly. You may want to run the
+following script to verify the availability of the mod_perl API.
+
+ use strict;
+ my $r = shift;
+ $r-send_http_header('text/html');
+ $r-print(It worked!!!\n);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
