Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harsh configure error when compiler is missing #1023

Open
eyalitki opened this issue Nov 22, 2024 · 0 comments
Open

Harsh configure error when compiler is missing #1023

eyalitki opened this issue Nov 22, 2024 · 0 comments

Comments

@eyalitki
Copy link

Background

When preparing to build the project on a clean machine (often a build container), the out-of-the-box error many developers (and devops engineers) get, is the following:

$ ./configure
Checking for gcc...
Compiler error reporting is too harsh for ./configure (perhaps remove -Werror).
** ./configure aborting.

The source of the error is that the compiler itself is missing, hence the compilation test returns an error. This error was reported in multiple places, such as here and here and was also encountered by my colleagues several times (hence my awareness to this issue).

Suggested Fix

Add an initial configure test that will check that the identified compiler (GCC/CC) is indeed installed on the machine, and report an indicate error otherwise. Example:

$ ./configure
Checking for gcc...
Failed to find an installed compiler.
** ./configure aborting.
eyalitki pushed a commit to eyalitki/zlib that referenced this issue Nov 22, 2024
Issue: madler#1023

Add a configure test that verifies the presence of the compiler
before we continue on using it in the following tests. If missing
return an indicative error to the user.

Signed-off-by: Eyal Itkin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant