Update php 4.3 RPM to php 5.3.3 php Post: 302799265

Sponsored Content

Operating Systems Linux Red Hat Update php 4.3 RPM to php 5.3.3 php Post 302799265 by monojcool on Friday 26th of April 2013 07:07:25 AM

04-26-2013

Registered User

Update php 4.3 RPM to php 5.3.3 php

Dear All,

My redhat version is:

[root@cotapplication3 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
[root@cotapplication3 ~]#

[root@cotapplication3 ~]# uname -a
Linux cotapplication3.cot.com 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
[root@cotapplication3 ~]#

I want to update my php from:

[root@cotapplication3 ~]# php -v
PHP 4.3.9 (cgi) (built: Aug 17 2005 10:24:09)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
[root@cotapplication3 ~]#

[root@cotapplication3 ~]# rpm -qa|grep php
php-ncurses-4.3.9-3.15
php-mysql-4.3.9-3.15
php-domxml-4.3.9-3.15
php-mbstring-4.3.9-3.15
php-devel-4.3.9-3.15
php-pgsql-4.3.9-3.15
php-imap-4.3.9-3.15
php-gd-4.3.9-3.15
php-4.3.9-3.8
php-odbc-4.3.9-3.15
php-snmp-4.3.9-3.15
php-pear-4.3.9-3.15
php-ldap-4.3.9-3.15
php-xmlrpc-4.3.9-3.15
[root@cotapplication3 ~]#

Above details is about my current configuration.

I want to update my php 4.3 to php 5.3.3

Please help me out to configure the above.

Thanks and Regards
Monoj Das

monojcool

View Public Profile for monojcool

Find all posts by monojcool

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installing php-4.3.3-2.i386.rpm

Ok when i try to run the install the is what i get How can i fix this can anyone help

2. UNIX for Dummies Questions & Answers

PHP rpm problem

I did not know where to ask this problem so posting it here The version of php used is 4.3.2. 1. If I say rpm -qa | grep php, I get mod_php4-4.2.2 and mod_php4-core-4.2.2 If I do php -v, I get 4.3.2. How could that be possible? I am sure the version which is being used is 4.3.2. 2. The...

3. UNIX for Advanced & Expert Users

Running multiple php scripts into one php only, cron mail alert problem...

hi, while separated they produce the usual mail alert and i can see the output... if i write into the php script: <?php system('php -f /var/www/vhosts/domain.com/httpdocs/folder/script1.php'); system('php -f /var/www/vhosts/domain.com/httpdocs/folder/script2.php'); system('php -f...

4. Red Hat

Installing PHP tools using RPM in Redhat Linux

Hi there, I am trying to install few PHP tools in my Linux server by creating RPMs from source ( tar.gz) files. The issue here is that the tar.gz files does not have a configure file and so I am not able to do ./configure make install opertations. I tried downloading src.rpms of these tools,...

LEARN ABOUT CENTOS

ksc

KSC(1)								   User Commands							    KSC(1)

NAME

       ksc - Linux kernel module source checker

SYNOPSIS

       ksc [ -d | --directory ] DIRECTORY

       ksc [ -k | --ko ] FILE

OPTIONS

       KSC   accepts  command-line  arguments,	and  has  both	a  long and short form usage.  You can use either style or combine them to specify
       options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules,	it
       checks for the specific architecture for which the binary was built.
       Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4

       -h, --help
	      show this help message and exit

       -c CONFIG, --config=CONFIG
	      path  to	the  local  ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from
	      /etc/ksc.conf

       -d DIRECTORY, --directory=DIRECTORY
	      path to the directory

       -i, --internal
	      to create text files to be used internally.

       -k KO, --ko=KO
	      path to the ko file.  You should either  use -d or -k to run the KSC tool, but not both.	If both -d and -k option is  used  at  the
	      same time then only -d is used and the -k option is discarded.

       -n RELEASENAME, --name=RELEASENAME
	      Red Hat release against which the bug is to be filed. Default value is 6.5

       -p PREVIOUS, --previous=PREVIOUS
	      path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.

       -r RELEASE, --release=RELEASE
	      RHEL whitelist release used for comparison

       -s, --submit
	      Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com).  The credentials need to be in the /etc/ksc.conf file. The
	      tool will prompt for bugzilla password.

	      The configuration file looks like below:

	      [bugzilla]
	      user=user@redhat.com
	      partner=partner-name
	      partnergroup=partner-group
	      server=https://bugzilla.redhat.com/xmlrpc.cgi

       -v, --version
	      Prints KSC version number

ksc - Version 0.9.11						     Feb 2014								    KSC(1)