https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86682
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to dschinn1001 from comment #0) > configure:2718: checking for gcc > configure:2745: result: /usr/local2/bin/gcc > configure:2983: checking for C compiler version > configure:2990: /usr/local2/bin/gcc --version >&5 > ./configure: line 2991: /usr/local2/bin/gcc: No such file or directory > configure:2993: $? = 127 > configure:3000: /usr/local2/bin/gcc -v >&5 > ./configure: line 3001: /usr/local2/bin/gcc: No such file or directory > configure:3003: $? = 127 > configure:3010: /usr/local2/bin/gcc -V >&5 > ./configure: line 3011: /usr/local2/bin/gcc: No such file or directory > configure:3013: $? = 127 > configure:3036: checking for C compiler default output file name > configure:3063: /usr/local2/bin/gcc conftest.c >&5 > ./configure: line 3064: /usr/local2/bin/gcc: No such file or directory This is not a GCC problem. You've told mcrypt's configure script to use a file that doesn't exist.
