-
Notifications
You must be signed in to change notification settings - Fork 402
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
FreeBSD Build fails: build sets invalid option '-Wno-nan-infinity-disabled' [-Werror,-Wunknown-warning-option] #7754
Comments
Link to #7730 looks like we don’t work with clang 18 yup |
Actually I would like to correct my original post. The problem occurs with clang-16. nan-infinity-disabled isn't known to the earlier clang which is elevated to error by -Werror. |
Hmm
I can't find where we set that. Is your build process changing flags somewhere? or have you changed the source of some of the libraries? |
Yeah i looked in your log. At the top is this
with the relevant section being
so it is definitely the case that if you set -Wno-nan-infinity-disabled and then use a compiler that doesn't support it with a package that compilers with Werror on, it will fail, because you've configured it in an error state I guess. Where does that segment come from? It's not me though so nothing to be done here I don't think! |
I couldn't find -Wno-nan-infinity-disabled either, but it appears after configure is done. In order to isolate from such issues, it's best to disable -Werror in production builds. |
NINJA is used to build it by the ports framework. |
The -Wno.... is in your log that you shared so it is definitely being added by your build system. I guess I could add a skip werror flag sure when i'm next in the cmake. but really the solution is to not add arbitrary build flags to the build! |
Oh or just add Wno-unknown-warning-option to the warnings we bypass I guess (and I suppose you could do the same in your eng to patch now). seems like there’s two things
and that should do it right? |
Ah, yes .... -Wno-nan-infinity-disabled' was added to mitigate this bug: #7730 |
Right. So where you added that perhaps also add -Wno-unknown-warning-option and then this one will be fixed until we fix 7730? See what I mean |
Yes, that's what I am doing. |
@yurivict Does this mean we can close this issue then? |
Ok, thanks. |
Bug Description:
See the log.
Surge XT Version
1.3.2
1.3.4
Reproduction Steps:
Regular build.
Expected Behavior:
A clear and concise description of what you expected to happen.
Screenshots:
If applicable, add screenshots/GIF/videos to help explain your problem.
Computer Information (please complete the following!):
Additional Information:
I think that the unknown warning -Wno-nan-infinity-disabled from some of the dependencies is elevated to the error status by the -Werror option that you set.
The text was updated successfully, but these errors were encountered: