easyapache failed after mysql upgrade

Mozafary

• August 10, 2014 23:32

Hello After upgrade mysql to 5.5,easyapache failed to rebuild apache/php with this error: configure: error: DOM extension requires LIBXML extension, add --enable-libxml checking whether to enable DBA interface... no checking whether to enable DOM support... yes configure: error: DOM extension requires LIBXML extension, add --enable-libxml !! './configure --disable-fileinfo --disable-libxml --disable-pdo --enable-bcmath --enable-calendar --enable-ftp --enable-gd-native-ttf --enable-magic-quotes --enable-sockets --prefix=/usr/lo$ !! Restoring original working apache !! !! Executing '/scripts/initsslhttpd' !!
I do: libxml64fix /scripts/autorepair rpm -e --nodeps zlib-devel rpm -e --nodeps libxml2-devel yum install zlib-devel yum install libxml2-devel run easyapache with "default" profile
but the problem still on our side. [COLOR="silver">- - - Updated - - - libxml64fix error: gcc -g -O2 -pedantic -W -Wformat -Wunused -Wimplicit -Wreturn-type -Wswitch -Wcomment -Wtrigraphs -Wformat -Wchar-subscripts -Wuninitialized -Wparentheses -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wredundant-decls -o .libs/xmllint xmllint.o ./.libs/libxml2.so -ldl -lz -lm ./.libs/libxml2.so: undefined reference to `gzopen64' collect2: ld returned 1 exit status make[1]: *** [xmllint] Error 1 make[1]: Leaving directory `/usr/local/cpanel/src/libxml2-2.6.28' make: *** [install-recursive] Error 1 Can't exec "/usr/local/cpanel/bin/checkperlmodules": No such file or directory at ./libxml64fix line 47.

• 

  cPanelMichael

  • August 11, 2014 19:25

  Hello :) The error message you provided suggests the solution is to add the "--enable-libxml" flag to /var/cpanel/easy/apache/rawopts/all_php5 before running EasyApache. You could do this by running a command such as: echo "--enable-libxml" > /var/cpanel/easy/apache/rawopts/all_php5
  Let us know if that helps. Note that I do see you have ticket number 5324749 open to address this issue as well. Feel free to let us know the outcome of that ticket. Thank you.

  0

Please sign in to leave a comment.