by Devin Yang
(This article was automatically translated.)

Published - 7 years ago ( Updated - 7 years ago )

gcc on CentOS is too old to support isfinite.

The built-in GCC 4.1.2 version of CentOS 5.11 is GCC ten years ago, and it will not be supported until GCC 4.3.3.
The new version of PHP configure cannot detect whether the old version of gcc supports isfinite.

So if you only have the old host, but you need to compile the new version of PHP in the CentOS 5 environment
You can change all ac_have_decl in configure to 0.

Tested in PHP 7.1.7, it does work. (You can use Vim to change it all at once)
if test "x$ac_cv_have_decl_isfinite" = xyes; then :
ac_have_decl=1 #Modified to ac_have_decl=0
else
ac_have_decl=0
the fi

Re-run ./configure . If make has failed before, remember to run make clean .

Tags: php

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


php,docker,dlaravel

A brief introduction to the phpenv container environment I built

I don't have time to shoot an introduction video, so I'll just grab some pictures and introduce the container environment deviny/phpenv I use. https://github.com/DevinY/phpenvphpenv can be regarded as an evolutionary version of my previous D-Laravel open source project, conceptually extending the use of many Dlaravel operation methods. The update of the container tends to be controlled by the user to build his own image, so I am not very good at changing the version number. In fact, the php version number of D-Laravel seems to have not been changed for a long time:p

php openssl curl

Fix CA setting problem

Sometimes the ca file cannot be found due to PHP version update or environment change. fix is ​​easy

docker,phpenv

Ran out of Docker IPv4 address pool problem solving

Maybe in the old version of the docker environment, when using Docker compose to start the container, you will encounter the following error: Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network This is actually this It is a symptom of running out of default-address-pools. In some environments, docker-compose will use the private network of Class B by default. The private IP of segment 172 has a range, from 172.16.0.0 to 172.31.255.255. That is to say, when we start a docker-compose Project, it will eat a private section of Class B, which is very heroic.