On a newly installed server with CentOS 7 I get a error when trying to rekompile m4 by doing ./build m4, please look into this bug an confirm it? Here is the error from output:
Update: My glibc version is: glibc-2.17-78.el7.x86_64 - it could be related to a incompatibility between m4-1.14.6 and Glibc-2.17: http://www.linuxquestions.org/questions/slackware-14/m4-need-some-love-4175471638/#post5000466
Edit: I think the problem might be fixed by upgrading m4 1.4.16 to the newest 1.4.17. Hope you can add m4 1.4.17 to custombuild: http://www.gnu.org/software/m4/m4.html
Update: m4 1.4.17 is now available in custombuild, and there is not any errors when recompiling the newest version. So the problem is solved.
Code:
make all-am
make[3]: Entering directory `/usr/local/directadmin/custombuild/m4-1.4.16/lib'
gcc -std=gnu99 -I. -g -O2 -MT gl_avltree_oset.o -MD -MP -MF .deps/gl_avltree_oset.Tpo -c -o gl_avltree_oset.o gl_avltree_oset.c
mv -f .deps/gl_avltree_oset.Tpo .deps/gl_avltree_oset.Po
gcc -std=gnu99 -I. -g -O2 -MT c-ctype.o -MD -MP -MF .deps/c-ctype.Tpo -c -o c-ctype.o c-ctype.c
mv -f .deps/c-ctype.Tpo .deps/c-ctype.Po
gcc -std=gnu99 -I. -g -O2 -MT c-stack.o -MD -MP -MF .deps/c-stack.Tpo -c -o c-stack.o c-stack.c
mv -f .deps/c-stack.Tpo .deps/c-stack.Po
gcc -std=gnu99 -I. -g -O2 -MT clean-temp.o -MD -MP -MF .deps/clean-temp.Tpo -c -o clean-temp.o clean-temp.c
In file included from clean-temp.h:22:0,
from clean-temp.c:23:
./stdio.h:477:1: error: 'gets' undeclared here (not in a function)
_GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");
^
make[3]: *** [clean-temp.o] Error 1
make[3]: Leaving directory `/usr/local/directadmin/custombuild/m4-1.4.16/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/local/directadmin/custombuild/m4-1.4.16/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/directadmin/custombuild/m4-1.4.16'
make: *** [all] Error 2
*** The make has failed, would you like to try to make again? (y,n):Update: My glibc version is: glibc-2.17-78.el7.x86_64 - it could be related to a incompatibility between m4-1.14.6 and Glibc-2.17: http://www.linuxquestions.org/questions/slackware-14/m4-need-some-love-4175471638/#post5000466
Edit: I think the problem might be fixed by upgrading m4 1.4.16 to the newest 1.4.17. Hope you can add m4 1.4.17 to custombuild: http://www.gnu.org/software/m4/m4.html
Update: m4 1.4.17 is now available in custombuild, and there is not any errors when recompiling the newest version. So the problem is solved.
Last edited: