- Joined
- Feb 27, 2003
- Messages
- 8,500
Hello,
This is somewhat old, and suPhp is already end-of-life.
However, if you're running 0.7.1, there is version 0.7.2 which has a security fix:
http://suphp.org/Home.html
The 0.7.2 does not compile out of the box, it has many hoops to jump through, and after some time, I was also not able to get it compiled on FreeBSD at all (there might be a way, but I couldn't figure it out).
We're not able to offer any guarantees with this version.
In any case, if you want to try to get 0.7.2, you can do the following:
which may .. or may not work, depending on many factors.
Note, please allow 24 hours for it to rsync from files1 to the other mirrors.
In some cases, I had to update a few other things first:
before suPhp would compile at all.
For 0.7.2, I had to add a series of extra commands into the build script, prior to calling the configure.suphp command.
They are as follows:
which are quite rough, as the configure.ac file isn't exactly up to date... so doesn't work in all cases, which case, stick with
or convert over to fastcgi, mod_ruid2, or php-fpm, with CB2.
======================
Related errors:
Show stopper for FreeBSD:
Related URL: https://lists.marsching.com/pipermail/suphp/2013-June.txt
Good Luck!
John
This is somewhat old, and suPhp is already end-of-life.
However, if you're running 0.7.1, there is version 0.7.2 which has a security fix:
http://suphp.org/Home.html
The 0.7.2 does not compile out of the box, it has many hoops to jump through, and after some time, I was also not able to get it compiled on FreeBSD at all (there might be a way, but I couldn't figure it out).
We're not able to offer any guarantees with this version.
In any case, if you want to try to get 0.7.2, you can do the following:
Code:
cd /usr/local/directadmin/custombuild
./build update
./build set new_suphp yes
./build suphpNote, please allow 24 hours for it to rsync from files1 to the other mirrors.
In some cases, I had to update a few other things first:
Code:
./build autoconf
./build automake
./build libtoolFor 0.7.2, I had to add a series of extra commands into the build script, prior to calling the configure.suphp command.
They are as follows:
Code:
perl -pi -e 's/AM_CONFIG_HEADER/AC_CONFIG_HEADERS/' configure.ac
aclocal
libtoolize --force
automake --add-missing
autoreconf
Code:
./build set new_php no======================
Related errors:
Code:
[COLOR=#000000]configure: error: cannot find install-sh, install.sh, or shtool in c[/COLOR][COLOR=#000000]onfig "."/config[/COLOR]
Code:
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'.libtoolize: linking file `config/ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Code:
mod_suphp.c:47: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'suphp_module'
mod_suphp.c:59: error: expected specifier-qualifier-list before 'table'
mod_suphp.c:66: error: expected ')' before '*' token
mod_suphp.c:84: error: expected ')' before '*' token
mod_suphp.c:125: error: expected ')' before '*' token
mod_suphp.c:145: error: expected ')' before '*' token
mod_suphp.c: In function 'suphp_handle_cmd_engine':
mod_suphp.c:191: error: 'suphp_module' undeclared (first use in this function)
mod_suphp.c:191: error: (Each undeclared identifier is reported only once
mod_suphp.c:191: error: for each function it appears in.)Related URL: https://lists.marsching.com/pipermail/suphp/2013-June.txt
Good Luck!
John
