Discussion about CustomBuild

Will new custombuild still support a php5 and php4 configuration or is it going to be php5 and php6 only?

I upgraded a server to php5 recently since php4 is going EOL in june and had to install php4 cgi as quite a few people were using php4 only scripts. Approx 10% of people on the server so it seems php4 is more widely used then led to believe.
 
vandal, yes you can have both as CGI.

Chrysalis, 1.1 will support PHP4 and PHP5, if you'll upgrade to 1.2 then you'll only have a support for PHP5 and PHP6.
 
Hello, I have just set up a new box and when I run ./build all d I get the following error:
configure: error: utf8_mime2text() has new signature, but U8T_CANONICAL is missing. This should not happen. Check config.log for additional information.

*** There was an error while trying to configure php. Check the configure/suphp/configure.php5 file

I am using custom build 1.2 on a CentOS 5 box.
 
Is it safe (for our clients) to switch everything to PHP5? In other words what is the chance that their sites will stop working?

Jeff
 
jlasman said:
Is it safe (for our clients) to switch everything to PHP5? In other words what is the chance that their sites will stop working?

Jeff
Click to expand...

Very slim, unless they're running outdated scripts that aren't php5 compliant. There aren't many of those around anymore, and anything that IS existing is an exploit waiting to happen.

php5 is very safe .. it's php6 I'm concerned about now.
 
smtalk said:
vandal, yes you can have both as CGI.

Chrysalis, 1.1 will support PHP4 and PHP5, if you'll upgrade to 1.2 then you'll only have a support for PHP5 and PHP6.
Click to expand...

any other differences between 1.1 and 1.2?
 
It's the people that use their own custom code that are the highest risk, after upgrading to php5 I have had a few people telling me their sites stopped working and its their own code. I agree the code is old and insecure as some of them I found out had also been enabling register globals via htaccess to support old code. The problem is there is still a significant amount of people that rely on php4.
 
chatwizrd said:
First of all when asking do you want to run make again answer with a lower case n not upper case.

2. It gives you the error that you need to install autoconf program.

Try apt-get install autoconf or yum install autoconf
Click to expand...

yes, finaly , i only via yum install to do that , but can not via Custombuild !
 
Thanks for the info! :)

Will the jailed shell option be inside the DA-webinterface?
 
Hmm, but it kind of makes sense no?! I mean, to be able to choose between "regular" and "jailed" as shell options for a user (regular or reseller).

Edit: Feature put in. [link]
 
Last edited:
On Fedora Core 5 the same error with building automake:

Trying to make automake...
make: *** No targets specified and no makefile found. Stop.

*** The make has failed, do you want to try to make again? (y,n)
Click to expand...

Anyone solved this problem?
 
In build find doAll() and comment out automake, autoconf, libtool.
 
Hello,

I've got a problem with my new update... With new custombuild 1.1 (php4-cgi and php5-cgi with suphp-0.6.3) the directive "AddHandler x-httpd-php4 .php" (all the directives AddHandler are ignored) in .htaccess don't run, but when I create a file phpinfo.php4, PHP4 runs... What is the problem ?

Thanks. Bye.
 
Hello,

There was a recent change to the following files with custombuild:
/etc/httpd/conf/extra/httpd-php-handlers.conf
/etc/httpd/conf/extra/httpd-suphp.conf

The following directive encompases the AddHandlers:
Code: 
<FilesMatch "\.(inc|php|php3|php4|php5|phtml|phps)$">
I would guess it's related, but I'm not quite sure how it would be... as it should only affect the extensions in question and not .htaccess files.

John
 
You must log in or register to reply here.
Back
Top