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

configure: fix check for valid compiler flags with Clang #537

Closed
wants to merge 1 commit into from

Conversation

brad0
Copy link

@brad0 brad0 commented May 10, 2024

By default Clang reports unknown compiler flags as warnings
thus the valid compiler flags check fails to work properly.
Clang needs to have -Werror passed.

By default Clang reports unknown compiler flags as warnings
thus the valid compiler flags check fails to work properly.
Clang needs to have -Werror passed.
@rofl0r
Copy link
Contributor

rofl0r commented May 10, 2024

you gotta be kidding. you prefer to break anybody's build (even yours, when the next clang version comes out and has yet another new warning added) that gets any warning, despite how harmless or bogus it may be , just so the tinyproxy build you currently have appeals to your aesthetic sense of wanting a warning-free terminal in front of you.
just use CFLAGS="-Werror-unknown-warning-option" ./configure to make your build beautiful enough for your senses. (from #536)

@rofl0r rofl0r closed this May 10, 2024
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

Successfully merging this pull request may close these issues.

2 participants