<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.3790.2541" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>Purpose: to install
PHP5 next to PHP4 -- using 2 apache2.x daemons running simultaneously
with their own php(4|5).ini file on different ports 80 and 10080 (persay)
respectively on an FC4 dual AMD64 server with SATA dirves. </FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>Need: various
extensions and custom code to PHP4 not compatible with PHP5 that are required
functionality to the primary site which has been updated to PHP5 for added
features and functionality (mysqli and such).</FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>Possible scenarios
already conceived: </FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>- place a second web
server into the DMZ to add the deprecated functionality back into the
internal websites that was identical to what was replaced (ms-2kp, iis5, php4)
and cringe in fear from the security/stability issues this will put back on
the network.</FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>- place a second web
server into the DMZ that has the earlier version of the applications to return
the deprecated functionality on a linux equivalent to the aforementioned
replaced server.</FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006>+ [chosen] use the new FC4 server
(which has a little muscle to spare for this activity) run a second web service
that uses a piggy-back install of PHP4 instead of the default PHP5.</SPAN></DIV>
<DIV><SPAN class=352003920-18012006></SPAN> </DIV></FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>Issues: the PHP4
module not available for yum installation on FC4 with the default repositories,
thus custom install of source code. the configure script included with the
PHP4 source code look ONLY at the lib directories and none of the lib64 paths on
the x86_64 platform for the needed extensions: gd, jpeg, png, ttf, ming, ... and
the list goes on, but Ming and its supporting extensions are the primary
factor.</FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>Status: I am over
halfway through rewriting the configure script myself to look through both the
lib and lib64 directories for the desired files. I am fretful of possible
conflicts though from some 32-bit and some 64-bit libraries being loaded into
the lingle php binary.</FONT></SPAN></DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>Question(s): Is
there already a fc4.x86_64.src.rpm out there for PHP4 somewhere that would ease
my pain? Is there a howto/tutorial already written somewhere that i can follow
easier than greying more hairs than i have to over finding each
shell-conditional and appending more advanced logic then may be necessary? Can
someone come here and install it for me so i can have a beer
instead?</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><SPAN class=352003920-18012006><FONT face=Arial size=2>--Kit
DeKat</FONT></SPAN></DIV></BODY></HTML>