RE: upgrading php from 4.1.2 to 4.3.4
"Maclure, Scott" <[email protected]> Tue, 10 Feb 2004 13:18:47 -0000
| Newsgroups | gmane.linux.redhat.stronghold |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPartTM-000-87c6e311-e03a-4fec-8585-804dd3623fc3 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3EFD8.6A38832E" ------_=_NextPart_001_01C3EFD8.6A38832E Content-Type: text/plain; charset="iso-8859-1" Hi Joe, Thanks for the response! I forgot to mention that I'm running stronghold on a solaris box, not a redhat dist :) (not my choice). Normally you can upgrade php without recompiling apache by just using the: --with-apxs=/path-to-apache/bin/apxs flag when building php, assuming apache has been built with the "--enable-module=so" flag (which I believe stronghold 4 does) then modifying httpd.conf to have : LoadModule php4_module libexec/libphp4.so and AddType etc etc to get php running. Now the last 2 issues for me is: 1) The fact that the libphp4.so module is currently in "..stronghold/lib/modules/1.3" rather than "stronghold/libexec", and 2) That stronghold doesn't use a php.ini file, rather another file "/conf/php4.conf" which I'm worried about. Does that all make sense? Or was that nonsensical rambling? thanks, Scott -----Original Message----- From: Joe Orton [mailto:[email protected]] Sent: Tuesday, February 10, 2004 12:22 PM To: Maclure, Scott Cc: '[email protected]' Subject: Re: upgrading php from 4.1.2 to 4.3.4 Hi Scott, On Tue, Feb 10, 2004 at 09:41:17AM -0000, Maclure, Scott wrote: > I have a server that's running stronhold, running their latest php (4.1.2 I > believe), which is too old for the application I want to run on the server! > So, I wanted to upgrade the server to php 4.3.4 (latest recommended PHP > release). > > Now, usually I follow the instructions for vanilla apache here: > > http://uk.php.net/manual/en/install.apache.php > <http://uk.php.net/manual/en/install.apache.php> These instructions should be fine for compiling PHP against Stronghold too. You might want to remove the PHP package included with Stronghold first, by running: # bin/rpm --erase stronghold-php4 Regards, joe ------_=_NextPart_001_01C3EFD8.6A38832E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2656.60"> <TITLE>RE: upgrading php from 4.1.2 to 4.3.4</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>Hi Joe, </FONT> </P> <P><FONT SIZE=3D2>Thanks for the response! I forgot to mention that I'm = running stronghold on a solaris box, not a redhat dist :) (not my = choice).</FONT></P> <P><FONT SIZE=3D2>Normally you can upgrade php without recompiling = apache by just using the:</FONT> </P> <P><FONT SIZE=3D2>--with-apxs=3D/path-to-apache/bin/apxs</FONT> </P> <P><FONT SIZE=3D2>flag when building php, assuming apache has been = built with the "--enable-module=3Dso" flag (which I believe = stronghold 4 does) then modifying httpd.conf to have :</FONT></P> <P><FONT SIZE=3D2>LoadModule php4_module libexec/libphp4.so</FONT> <BR><FONT SIZE=3D2>and AddType etc etc to get php running.</FONT> </P> <P><FONT SIZE=3D2>Now the last 2 issues for me is:</FONT> <BR><FONT SIZE=3D2>1) The fact that the libphp4.so module is currently = in "..stronghold/lib/modules/1.3" rather than = "stronghold/libexec", and </FONT></P> <P><FONT SIZE=3D2>2) That stronghold doesn't use a php.ini file, rather = another file "/conf/php4.conf" which I'm worried = about.</FONT> </P> <P><FONT SIZE=3D2>Does that all make sense? Or was that nonsensical = rambling?</FONT> </P> <P><FONT SIZE=3D2>thanks,</FONT> <BR><FONT SIZE=3D2>Scott</FONT> </P> <P><FONT SIZE=3D2>-----Original Message-----</FONT> <BR><FONT SIZE=3D2>From: Joe Orton [<A = HREF=3D"mailto:[email protected]">mailto:[email protected]</A>]</FONT> <BR><FONT SIZE=3D2>Sent: Tuesday, February 10, 2004 12:22 PM</FONT> <BR><FONT SIZE=3D2>To: Maclure, Scott</FONT> <BR><FONT SIZE=3D2>Cc: '[email protected]'</FONT> <BR><FONT SIZE=3D2>Subject: Re: upgrading php from 4.1.2 to = 4.3.4</FONT> </P> <BR> <P><FONT SIZE=3D2>Hi Scott,</FONT> </P> <P><FONT SIZE=3D2>On Tue, Feb 10, 2004 at 09:41:17AM -0000, Maclure, = Scott wrote:</FONT> <BR><FONT SIZE=3D2>> I have a server that's running stronhold, = running their latest php (4.1.2 I</FONT> <BR><FONT SIZE=3D2>> believe), which is too old for the application = I want to run on the server!</FONT> <BR><FONT SIZE=3D2>> So, I wanted to upgrade the server to php 4.3.4 = (latest recommended PHP</FONT> <BR><FONT SIZE=3D2>> release).</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Now, usually I follow the instructions for = vanilla apache here:</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> <A = HREF=3D"http://uk.php.net/manual/en/install.apache.php" = TARGET=3D"_blank">http://uk.php.net/manual/en/install.apache.php</A></FO= NT> <BR><FONT SIZE=3D2>> <<A = HREF=3D"http://uk.php.net/manual/en/install.apache.php" = TARGET=3D"_blank">http://uk.php.net/manual/en/install.apache.php</A>>= </FONT> </P> <P><FONT SIZE=3D2>These instructions should be fine for compiling PHP = against Stronghold</FONT> <BR><FONT SIZE=3D2>too. You might want to remove the PHP package = included with Stronghold</FONT> <BR><FONT SIZE=3D2>first, by running:</FONT> </P> <P><FONT SIZE=3D2> # bin/rpm --erase stronghold-php4</FONT> </P> <P><FONT SIZE=3D2>Regards,</FONT> </P> <P><FONT SIZE=3D2>joe</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C3EFD8.6A38832E-- ------=_NextPartTM-000-87c6e311-e03a-4fec-8585-804dd3623fc3 Content-Type: text/plain; name="Mail_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Mail_Disclaimer.txt" The information contained in or attached to this email is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are not authorised to and must not disclose, copy, distribute, or retain this message or any part of it. It may contain information which is confidential and/or covered by legal professional or other privilege (or other rules or laws with similar effect in jurisdictions outside England and Wales). The views expressed in this email are not necessarily the views of Centrica plc, or Centrica Telecommunications Limited, and their directors, officers or employees make no representation or accept any liability for its accuracy or completeness unless expressly stated to the contrary. ------=_NextPartTM-000-87c6e311-e03a-4fec-8585-804dd3623fc3--