Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
=====================================================================
FAILED TEST SUMMARY
---------------------------------------------------------------------
Bug #38474 (getAttribute select attribute by order, even when prefixed) (OK to fail with libxml2 < 2.6.2x) [ext/dom/tests/bug38474.phpt]
Bug #42082 (NodeList length zero should be empty) [ext/dom/tests/bug42082.phpt]
libgd #106 (imagerectangle 1x1 draws 1x3) [ext/gd/tests/libgd00106.phpt]
Bug #16069 (ICONV transliteration failure) [ext/iconv/tests/bug16069.phpt]
iconv stream filter [ext/iconv/tests/iconv_stream_filter.phpt]
=====================================================================
So I took a gamble and did make install.
I was previously running php as a CGI - and as the new install did not seem to switch over to the new CGI - I checked and it appeared that the /var/www/cgi-bin/php file was still 5.1.6
With this in mind, I found php5-cgi in /usr/bin - so I cp /usr/bin/php5-cgi /var/www/cgi-bin/php which overwrote the old php5.1.6 file.
After I did that - phpinfo(); now shows the new install 5.2.4 and all seems to be working fine (and a little faster?)
Did I do ok copying the php5-cgi file and renaming it? or was that wrong for some reason? it does all appear to work?
Also, could someone give me a pointer on the following comment that the make install through out:
You may want to add: /usr/lib64/php to your php.ini include_path
well that's not an upgrade that's the start of making a system just about unusable through mis-management! by the sound of it you still have the original rpm for php installed? you really should remove the new version and then upgrade the existing rpm to a newer version e.g. http://rpm.pbone.net/index.php3/stat...86_64.rpm.html
well that's not an upgrade that's the start of making a system just about unusable through mis-management! by the sound of it you still have the original rpm for php installed? you really should remove the new version and then upgrade the existing rpm to a newer version e.g. http://rpm.pbone.net/index.php3/stat...86_64.rpm.html
Hi,
It was installed from source before and upgraded as such by a hired hand to 5.1.6
you've still overwritten part of an existing installation. you need to remove the old stuff first. is the source directory for it still around? if so, a make uninstall in that old directory should clear it all out too.
you've still overwritten part of an existing installation. you need to remove the old stuff first. is the source directory for it still around? if so, a make uninstall in that old directory should clear it all out too.
Thanks for responding.
I do have the original src directory.
If I was to do a make uninstall to remove the old 5.1.6 files would it still leave the existing 5.2.4 working?
If not - would installing the rpm you mentioned in the post above pickup on my existing configure line...
it depends what options were passed to both source builds as to whether they will completely overlap, partially overlap or be completely independent. the rpm would be completely prebuilt, your source wouldn't relate at all to how it is built. is there a specific feature that you know you need to enable which is non standard? your life will be much simpler if you can live with standard builds.
it depends what options were passed to both source builds as to whether they will completely overlap, partially overlap or be completely independent. the rpm would be completely prebuilt, your source wouldn't relate at all to how it is built. is there a specific feature that you know you need to enable which is non standard? your life will be much simpler if you can live with standard builds.
if you still have the new version, then you can reinstall it as many times as you want, so i'd say uninstall everything possible and install the rpm. you can then rpm "php -i" to see exactly what it was built with, or rather the ./configure command that the packager ran. many options are going to be there by default, so won't show up, but those rpm's are packaged to suit most peoplem so i'd be confident you'll be ok.
if you still have the new version, then you can reinstall it as many times as you want, so i'd say uninstall everything possible and install the rpm. you can then rpm "php -i" to see exactly what it was built with, or rather the ./configure command that the packager ran. many options are going to be there by default, so won't show up, but those rpm's are packaged to suit most peoplem so i'd be confident you'll be ok.
Any ideas on how to manually remove the current install of php?
Thanks
Tony
Sorry to bump an old thread... but..
As PHP 5.2.5 is out - would a make uninstall on the 5.2.4 (which was rolled over the top of 5.1.6 - see above) help remove everything so that I can start again with an RPM?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.