-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
qt5.{qtwebengine, qtwebkit}: fix -Wno-class-memaccess warning for clang #70544
Conversation
Links to broken builds: https://hydra.nixos.org/build/102530965 |
@@ -54,9 +54,9 @@ qtModule { | |||
[ | |||
# with gcc7 this warning blows the log over Hydra's limit | |||
"-Wno-expansion-to-defined" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But this one gets ignored?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this one is actually supported in clang: https://clang.llvm.org/docs/DiagnosticsReference.html#wexpansion-to-defined
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify my phrasing/use of "ignore" - with GCC it's the default to ignore non-existent warning options. With clang it's afaik not. There is -Wno-unknown-warning-option
for that, which we don't use as far as I can tell.
@GrahamcOfBorg build qt5.qtwebengine |
hmm, I guessing will probably timeout on darwin and ofborg in general. A darwin tester is probably needed (or builder access). |
@worldofpeace: I briefly tried it out running the beginning of the build on NixOS by overriding |
Ahh @d-goldin, I guess it's sufficient to switch it out for clang. Will try that 👍 |
Hmm, I'm not sure how I can do that with these qt expressions... |
@worldofpeace: I tried it with |
Uhm, but you know what - I looked at the log again, and I got misled by the warning about the wrong flag. This does not actually seem to cause issues with the build itself (at least log length due to warning does not seem problematic either at this stage) so I guess it's a "nice to make it cleaner" but did not actually break the builds. Really sorry for the hassle, my bad :( |
With a previous fix for log size issues due to GCC 8 a gcc specific `-W` flag was added that clang does not know, so it spams the logs.
fa3375a
to
3bfe087
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this on darwin. As expected, this doesn't fix the builds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
backported in 9bbad4c |
Motivation for this change
With a previous fix for log size issues due to GCC 8.a gcc specific
-W
flag was added that clang doesnot gracefully ignore
See comment #70544 (comment)
This does not break the build, it just logs unneeded warnings and the breakage is somewhere else.
This was done in #68434 and #68869
We forgot to test this with clang and/or on darwin.
cc @worldofpeace
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @