> Along these lines, I see in your guide that you say that perl and
> mod_perl have to be compiled with the same compiler. So if I am
> planning on recompiling Apache and mod_perl with pgcc to give me the two
> server setup, I will need to recompile Perl as well.
I might be wrong, but I think perl's MakeMaker enforces the compiler to be
the same as used for Perl. It takes the info from Config.pm. Am I wrong?
> I am doing this on a live server. What do I need to do to stop my current
> Perl setup working in case everything goes horribly wrong? (my fear is that
> recompiling perl will overwrite some libraries that the running system
> needs)
>
> Could I recompile perl in a new directory, then change a symlink over from
> one binary to the other and all would be OK? Or is it more complex than
> that.
First yes, you can compile it in another directory (look for the
'--prefix' in the configure scripts, but you will have to recompile
mod_perl as well, otherwise it wouldn't work.
But, why should you do it on a live server? Prepare an indentical box
(what can be easier if you are using RH or other out-of-box OS), build and
test the new binaries/perl/mod_perl/whatever, test them that they work
then either swicth the boxes or install the tested sw on a live box. Use
RPM or other packaging utility to make the upgrade errorprone and easy.
Prepare a SRC RPM, make a binary, test that it installs correctly and when
you are ready, copy it (them) onto a target machine and install...
Should be an easy task to accomplish.
Tweaking a live server is a dangerous thing!
_______________________________________________________________________
Stas Bekman mailto:[EMAIL PROTECTED] www.singlesheaven.com/stas
Perl,CGI,Apache,Linux,Web,Java,PC at www.singlesheaven.com/stas/TULARC
www.apache.org & www.perl.com == www.modperl.com || perl.apache.org
single o-> + single o-+ = singlesheaven http://www.singlesheaven.com
