-
-
Notifications
You must be signed in to change notification settings - Fork 350
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
CI integration of NUT for Windows builds - go (semi-)native with MSYS2 provided clang on Windows #1651
Comments
It compiled stuff almost well, except the C++ code where it failed to However for linking it calls
|
Retrying with a hack in local workspace to just avoid that option so far (needed for CLANG to report all issues and not bail out after 10 or 20), and to keep reporting all warnings as errors in the quick
...and waiting for results... |
Verdicts seen so far:
Typically the same stack is seen for the wrappers:
|
We probably need a relaxed At least hacking into generated
Further replacing Finally a re-run with |
For now throwing in a towel at this on my side, it was not a low hanging fruit and I have some higher priorities at the time. A quick fix attempt by setting and Not sure how to easily detect that clang uses gcc as the linker (other than trying to link in configure and looking at success and/or stderr text?) so as to not use flags incompatible with GCC in this scenario. Note that a similar investigation in #1647/#1650 uses (I think) a complete llvm-mingw clang stack including the FWIW the anti-warning C code fixes above (adding |
For kicks, finally got around to try "standard-issue" pre-set environment "MSYS2 MinGW Clang x64" in the semi-native build environment, with current
master
branch (same asv2.8.0-Windows
tag at the moment):Prepare filenames (and ccache):
Then go NUT:
Let's see what pops out...
For related efforts and discussions, see also:
The text was updated successfully, but these errors were encountered: