Moving PHP 5.2 from Server to Server: Compilation and Dependencies

When planning to migrate a compiled source code, such as PHP 5.2, from one server to another, it's essential to consider the potential dependencies that may be missing on the target machine. In this scenario, we're dealing with two identical CentOS 6.5 servers running Plesk 12, and our goal is to transfer a compiled version of PHP 5.2.17 from Server 1 to Server 2.

The first question that arises is whether it's possible to simply copy the compiled source code over to the new server and activate it within Plesk. While this approach might seem straightforward, there's a risk of missing dependencies that could lead to issues with the PHP installation. To avoid any potential problems, compiling PHP 5.2.17 from source on each machine is a more reliable option.

Server 1, which currently runs the compiled PHP 5.2.17, has been configured with specific compiler tools and software installed for this purpose. In contrast, Server 2 lacks these essential components. To ensure a smooth transition, compiling PHP 5.2.17 from source on Server 2 will guarantee that all dependencies are met.

When comparing the results of PHP bench tests between PHP 5.3, PHP 5.4, and PHP 5.5, it's clear that each version has its advantages and disadvantages. However, for this specific scenario, we're focused on migrating a legacy version of PHP 5.2.17.

In conclusion, while copying the compiled source code might seem like an efficient solution, compiling PHP 5.2.17 from source on Server 2 is the recommended approach to ensure that all dependencies are met and the installation runs smoothly. This will enable us to transfer the PHP 5.2.17 installation to Server 2 without encountering any issues related to missing dependencies.

Centos 6.5 install php 5.2