The error message as in the title of this article is real. It is an output of executing a certain command. That certain command is a command for compiling a source files. The compilation process has the following output presenting the error message :
[root@localhost postgresql-11.1]# ./configure --prefix=/opt/postgresql-11.1/app checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking which template to use... linux checking whether NLS is wanted... no checking for default port number... 5432 checking for block size... 8kB checking for segment size... 1GB checking for WAL block size... 8kB checking for gcc... no checking for cc... no configure: error: in `/opt/postgresql-11.1/src/postgresql-11.1': configure: error: no acceptable C compiler found in $PATH See `config.log' for more details [root@localhost postgresql-11.1]#
For an example, the above context is about compiling the PostgreSQL Database source files. So, in order to solve the above problem, the following are steps for solving it :
1. Since the problem is about no C compiler found in the command execution path, just install it. In this case, the operating system is CentOS. The first attempt is to install Development Tools package group. By then, execute the following command :
yum group install "Development Tools"
2. But in this article, there is only one package for further installation to solve the above problem. Just install the ‘gcc’ package. So, there is no need to install several packages exist in the Development Tool group package. Type the following command :
yum install gcc
3. After successfully executing the above command, just continue the previous process. Start to compile the PostgreSQL Database source files. The following output of the command appears :
[root@localhost postgresql-11.1]# ./configure --prefix=/opt/postgresql-11.1/app checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking which template to use... linux checking whether NLS is wanted... no checking for default port number... 5432 checking for block size... 8kB checking for segment size... 1GB checking for WAL block size... 8kB checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no 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 ISO C89... none needed checking for g++... no checking for c++... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking whether gcc supports -Wdeclaration-after-statement, for CFLAGS... yes checking whether gcc supports -Wendif-labels, for CFLAGS... yes checking whether g++ supports -Wendif-labels, for CXXFLAGS... no checking whether gcc supports -Wmissing-format-attribute, for CFLAGS... yes checking whether g++ supports -Wmissing-format-attribute, for CXXFLAGS... no checking whether gcc supports -Wformat-security, for CFLAGS... yes checking whether g++ supports -Wformat-security, for CXXFLAGS... no checking whether gcc supports -fno-strict-aliasing, for CFLAGS... yes checking whether g++ supports -fno-strict-aliasing, for CXXFLAGS... no checking whether gcc supports -fwrapv, for CFLAGS... yes checking whether g++ supports -fwrapv, for CXXFLAGS... no checking whether gcc supports -fexcess-precision=standard, for CFLAGS... yes checking whether g++ supports -fexcess-precision=standard, for CXXFLAGS... no checking whether gcc supports -funroll-loops, for CFLAGS_VECTOR... yes checking whether gcc supports -ftree-vectorize, for CFLAGS_VECTOR... yes checking whether gcc supports -Wunused-command-line-argument, for NOT_THE_CFLAGS... no checking whether gcc supports -Wformat-truncation, for NOT_THE_CFLAGS... no checking whether gcc supports -Wstringop-truncation, for NOT_THE_CFLAGS... no checking whether the C compiler still works... yes checking how to run the C preprocessor... gcc -E ...
In summary, according to the above output of the command, the solution is very simple. The achievement for solving the problem is only by installing gcc package.