Discussion about CustomBuild

Martynas,

Still have troubles with suphp (automake / autoconf error: Lc-local or so what) on two CentOS5/32 boxes. Does PHP need to be CLI or CGI?
 
CLI is default :) But if you want to use suPHP - you must have PHP as CGI. Could you post the error output here?
 
Code: 
[root@adam custombuild]# ./build suphp
Found /usr/local/directadmin/custombuild/suphp-0.6.2.tar.gz
Extracting ...
Done.
Configuring suphp-0.6.2...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether build environment is sane... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for correct ltmain.sh version... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... cat: ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... cat: ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for APR... yes
checking for dynamic Apache module support (via APXS)... found at /usr/sbin/apxs (version 2.2.6)
checking for set-UID/set-GID mode... ok - using paranoid
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/apache/Makefile
config.status: creating src/apache2/Makefile
config.status: creating src/config.h
config.status: executing depfiles commands
Done Configuration.
Trying to make suPHP...
cd . && /bin/sh /usr/local/directadmin/custombuild/suphp-0.6.2/config/missing --run aclocal-1.9
acinclude.m4:43: warning: underquoted definition of APR_FIND_APR
  run info '(automake)Extending aclocal'
  or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
aclocal:configure.ac:24: warning: macro `AM_PROG_LIBTOOL' not found in library
 cd . && /bin/sh /usr/local/directadmin/custombuild/suphp-0.6.2/config/missing --run automake-1.9 --gnu
src/apache/Makefile.am:8: Libtool library used but `LIBTOOL' is undefined
src/apache/Makefile.am:8:
src/apache/Makefile.am:8: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/apache/Makefile.am:8: to `configure.ac' and run `aclocal' and `autoconf' again.
src/apache2/Makefile.am:10: Libtool library used but `LIBTOOL' is undefined
src/apache2/Makefile.am:10:
src/apache2/Makefile.am:10: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/apache2/Makefile.am:10: to `configure.ac' and run `aclocal' and `autoconf' again.
make: *** [Makefile.in] Error 1

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

Boxes: CentOS5/32bit (login on request, located in Amsterdam, EU)
 
Try:
Code: 
./build autoconf; ./build automake; ./build libtool; ./build suphp
 
Still does'nt work

Code: 
Trying to make suPHP...
cd . && /bin/sh /usr/local/directadmin/custombuild/suphp-0.6.2/config/missing --run aclocal-1.9
acinclude.m4:43: warning: underquoted definition of APR_FIND_APR
  run info '(automake)Extending aclocal'
  or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
aclocal:configure.ac:24: warning: macro `AM_PROG_LIBTOOL' not found in library
 cd . && /bin/sh /usr/local/directadmin/custombuild/suphp-0.6.2/config/missing --run automake-1.9 --gnu
src/apache/Makefile.am:8: Libtool library used but `LIBTOOL' is undefined
src/apache/Makefile.am:8:
src/apache/Makefile.am:8: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/apache/Makefile.am:8: to `configure.ac' and run `aclocal' and `autoconf' again.
src/apache2/Makefile.am:10: Libtool library used but `LIBTOOL' is undefined
src/apache2/Makefile.am:10:
src/apache2/Makefile.am:10: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/apache2/Makefile.am:10: to `configure.ac' and run `aclocal' and `autoconf' again.
make: *** [Makefile.in] Error 1

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

options.comf
Code: 
#PHP settings. default_php possible values - 4 or 5
default_php=5
php4_cli=yes
php4_cgi=no
php5_cli=no
php5_cgi=yes
zend=no

#Possible values - 5.0 or 5.1 (4.1 is possible too, but it's EOL)
mysql=5.0
mysql_inst=yes

#Possible values - 1.3, 2.0 or 2.2
apache_ver=2.2

#Web applications
phpmyadmin=yes
squirrelmail=no
roundcube=yes

#Mail options
mail-header-patch=yes
dovecot=yes
eximconf=yes

#FTP options
proftpd=yes

#Custombuild options
clean=yes
 
Last edited:
Do you have any suggestions for this FAQ? :) Do I have anything to add?
 
Randy, try to search CentOS forums (I'm sure you'll find a solution).
 
MySQL 5.0 has a new password system, and PHP cannot connect to it because it cannot send a correct password. You must use the MySQL command OLD_PASSWORD() when adding a user to the database, or PHP cannot connect as of the library that comes with PHP 5.0Beta3

How do I fix this?
 
Installing PEAR environment: /usr/local/lib/php/
Segmentation fault (core dumped)
*** Error code 139

Stop in /usr/local/directadmin/custombuild/php-5.2.4.
*** Error code 1

Stop in /usr/local/directadmin/custombuild/php-5.2.4.

*** The install has failed, do you want to try to install it again? (y,n):

and this is always repeating, no matter what i do... installing from ports doesn't give such problems... where am i wrong?
 
Roundcube: Unable to connect to the database!

I can login as da_roundcube in phpmyadmin, however when going to roundcube I get

DATABASE ERROR: CONNECTION FAILED!

Unable to connect to the database!


Any ideas?
 
CrazyLane, run "./build roundcube" again :) Maybe database password isn't right in RoundCube configuration file.
 
Are you sure MySQL is up and running? (and you have /var/lib/mysql/da_roundcube)
 
Yes it does, I can access it via cmd and phpmyadmin, however I just checked and all of my databases(USER) now cannot connect to database.

I did install ELS recently, any ideas?
 
Ah, I think you have sql.safe_mode set to on in /usr/local/lib/php.ini :) Set it to off and restart the apache service. Good luck! :)
 
They aren't created yet. You can create "custom" directory in /usr/local/directadmin/custombuild. There you'll need to create the same file as it is in configure directory (then you can edit it). E.g. if you want to have a custom PHP5 configuration for Apache2, just create /usr/local/directadmin/custombuild/custom/ap2/configure.php5 file, and it will automatically detect it (and will use everything from it instead of configure/ap2/configure.php5 file).
 
smtalk said:
They aren't created yet. You can create "custom" directory in /usr/local/directadmin/custombuild. There you'll need to create the same file as it is in configure directory (then you can edit it). E.g. if you want to have a custom PHP5 configuration for Apache2, just create /usr/local/directadmin/custombuild/custom/ap2/configure.php5 file, and it will automatically detect it (and will use everything from it instead of configure/ap2/configure.php5 file).
Click to expand...
ok.. now i know.
i previously had mod_security and mod_evasive installed on my server but custom build recompiled apache and it seems to have disappeared. any fixes? possible to include these two in the next release of custom build?
oh and where do you get version 1.2 of custombuild?
 
I'm the creator of the CustomBuild script, and I'm developing 1.2 (it's closed beta now).
 
smtalk said:
I'm the creator of the CustomBuild script, and I'm developing 1.2 (it's closed beta now).
Click to expand...
yea i know you created it but in your first post you seemed to mention as though v1.2 was the current release version.
so any fix for the mod_security/evasive issues?

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