Description: Trying to produce clang static analysis reports on Windows (using cygwin and LLVM 11.0.0 base install) using the scan-build-report.sh script does not work. Here is the output from scan-build-report.log (during the run of autogen.sh from scan-build-report.sh): configure: found Visual C++ 2019 checking ccc-analyzer is at least Visual Studio 2019 version 16.5... configure: error: no Error running configure at ./autogen.sh line 316. scan-build: Analysis run complete. scan-build: Removing directory '/tmp/scan-build-2021-02-16-232603-12829-1' because it contains no reports. scan-build: No bugs found. Error: Failed to run scan-build ./autogen.sh Note that my Visual Studio install is Version 16.8.4 which is >16.5. Steps to Reproduce: 1. Do preqs from https://wiki.documentfoundation.org/Development/BuildingOnWindows , then launch a cygwin shell (I'm using x86_64 version) 2. Check out core repo (e.g. git clone https://gerrit.libreoffice.org/core libo-core) 3. Check out dev-tools repo (e.g. git clone https://gerrit.libreoffice.org/dev-tools dev-tools) 4. cd to dev-tools/scan-build-report 5. Run "./scan-build-report.sh -s /cygdrive/<path to core> -o /cygdrive/<path to output somewhere>" Actual Results: scan-build fails. See description for failure details. Expected Results: scan-build runs and produces clang static analysis reports in the output directory specified. Reproducible: Always User Profile Reset: No Additional Info: n/a
Also, when running "scan-build -o <output_dir> make" (which is the run after autogen.sh in scan-build-report.sh) for example under core/vcl you will see the many of the following errors: error: invalid integral value 'd' in '-Od' This is because the compiler is replaced with c++-analyzer and doesn't like the command line args.
Dear Matt K, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug