Understanding Makefile Error 127
In Unix-like systems, exit code 127 is universally reserved for "command not found." When you run make to compile Nginx from source, the process executes a series of scripts and checks defined in the Makefile. If any of these steps attempt to call an external program—such as gcc, perl, or specific OpenSSL utilities—and that program is not installed or not accessible via the $PATH variable, the script exits immediately with code 127.
The error message itself is rarely descriptive enough to identify the missing component on its own. It usually appears as:
make[1]: *** [conf] Error 127
make: *** [build] Error 2This generic output forces you to look at the lines immediately preceding the error in your terminal output. You will likely see a line attempting to execute a command like ./configure --with-openssl=... followed by the failure. The root cause is almost always related to missing development headers or build tools rather than syntax errors in the Nginx source code itself.
Identifying Missing Dependencies
The most common culprit for this error during Nginx compilation is the absence of OpenSSL development libraries. Nginx relies heavily on OpenSSL for HTTPS support. If you specified --with-ssl or --with-http_ssl_module during configuration, the build system searches for OpenSSL headers and binaries. If they are missing, the configure step fails with a 127 error because it cannot find the necessary tools to verify the installation.
Another frequent cause is the lack of a C compiler. While less common on modern servers, if gcc or cc is not installed, the compilation phase will fail instantly. Similarly, tools like perl or libpcre3-dev may be required depending on your Nginx version and configuration options. To diagnose which specific tool is missing, run the ./configure command again manually and watch the output closely. Look for lines ending in "command not found" or similar messages before the final error.
If you are using a minimal Linux distribution, you might have the base runtime libraries but not the development headers. For example, having openssl installed is not sufficient; you need libssl-dev (Debian/Ubuntu) or openssl-devel (RHEL/CentOS). Without these headers, the build system cannot locate the static or shared objects needed for linking.
Solving the Issue on Debian and Ubuntu
On Debian-based systems, you can resolve most dependency issues by installing the build essentials and specific library packages. Open your terminal and run the following command to install the necessary compilers, linkers, and development headers:
sudo apt-get update
sudo apt-get install build-essential libpcre3 libpcre3-dev zlib1g zlib1g-dev libssl-devThis command installs gcc, make, PCRE development files for regular expression support, Zlib for compression, and OpenSSL development libraries. After running this, clean your previous build artifacts by deleting the Makefile and re-running ./configure. The error should disappear if the dependencies were indeed the issue.
If you are compiling against a custom version of OpenSSL rather than the system package, ensure that the path to your custom OpenSSL installation is correctly specified in the ./configure command using --with-openssl=/path/to/openssl. Additionally, verify that the LDFLAGS and CFLAGS environment variables include the paths to your custom library’s lib and include directories.
Solving the Issue on RHEL, CentOS, and Fedora
For Red Hat-based distributions, the package names differ slightly. Use yum or dnf to install the required components:
sudo yum groupinstall "Development Tools"
sudo yum install pcre pcre-devel zlib zlib-devel openssl openssl-develThe "Development Tools" group ensures that gcc, make, and other essential build utilities are present. The subsequent commands install the specific libraries needed for Nginx modules. Once installed, proceed with cleaning the build directory and reconfiguring.
If you encounter persistent errors after installing these packages, check your system’s $PATH variable. Occasionally, non-standard installations of OpenSSL or Perl may reside in directories not included in the default search path. You can append custom binary directories to your $PATH temporarily during the build process to ensure the configure script can locate them.
Verifying the Fix
After installing the dependencies, it is crucial to clear any cached configuration data from previous failed attempts. Delete the existing Makefile and any config.status files in the Nginx source directory. Then, re-run the ./configure script with your desired options. If the configuration completes without errors, you can safely run make and make install.
For users managing complex builds, consider automating dependency installation. Some community guides suggest creating a wrapper script that checks for the existence of critical commands like gcc and openssl before proceeding. This proactive approach prevents silent failures where the build starts but crashes later due to missing tools. For more advanced deployment scenarios involving containerization, refer to our guide on Effortlessly Copy Data Using a Customized Makefile in Docker Nginx Installation to streamline your workflow.
Frequently Asked Questions
What does Exit Code 127 mean in Linux?
Exit code 127 indicates that the shell could not find the requested command. In the context of compilation, it means a required build tool or utility is either not installed or not located in your system's PATH environment variable.
Can I ignore Error 127 and continue building?
No, you cannot ignore this error. It represents a fatal failure in the build process. Continuing without resolving the missing dependency will result in a broken or incomplete Nginx binary that lacks essential features like SSL support.
Why do I get Error 127 even though GCC is installed?
If GCC is installed but you still see this error, another dependency such as OpenSSL, PCRE, or Perl is likely missing. The build system checks for multiple tools sequentially; the error points to the first one it cannot find, which may not be the compiler itself.
How do I find which package provides a missing command?
You can use the apt-file command on Debian/Ubuntu or yum provides on RHEL/CentOS to search for the package containing the missing executable. For example, running apt-file search bin/perl helps identify which package installs the Perl interpreter.
Does this error occur when installing Nginx via apt?
No, this error only occurs when compiling Nginx from source code. When you install Nginx using package managers like apt or yum, the pre-compiled binaries and their dependencies are handled automatically, bypassing the manual build process entirely.