php from current to stable

Wed · 01-03-2011, 07:39 AM

I have tried for some time to compile and install PHP 5.3.4 on my web server with Slack 13.1 (32-bit). But failed in quite a few ways. Now I got the package from current and installed it.

I realize that I'm taking a risk. But how severe could the consequences be?

willysr · 01-03-2011, 09:26 AM

why don't you use SlackBuild from -Current to build your own PHP package?

Wed · 01-03-2011, 03:57 PM

I should have thought of that. Well, I hope I won't get bitten by the precompiled package.

Wed · 01-04-2011, 02:18 PM

The precompiled package from current left some stuff to be wished for. Hopefully, the slackbuild will perform better. But it doesn't look exactly like all the other slackbuilds I have installed.

Do I simply recreate the complete directory, including the empty pear-directory? Or is there some file/s that I don't need?

Code:

File:doinst.sh.gz
File:mod_php.conf.example
pear
File:php-5.3.4.tar.xz
File:php.CVE-2010-4409.diff.gz
File:php.SlackBuild
File:php.ini-development.diff.gz
File:slack-desc

I'll give it a whirl anyway.

Wed · 01-04-2011, 03:23 PM

The slackbuild from current demanded alpine as well. Ok, no big deal really. But I'm baffled. Anyway, I get this message after a while:

Code:

checking for utf8_mime2text signature... new
checking for U8T_DECOMPOSE... 
configure: error: utf8_mime2text() has new signature, but U8T_CANONICAL is missing. This should not happen. Check config.log for additional information.
make: *** No targets specified and no makefile found.  Stop.
make: *** No targets specified and no makefile found.  Stop.
bash-4.1$ ls

Are there many packages I need to finish this? And I don't have a config.log.