I’m using Build Wrapper to compile the database for analyzing my C++ source code. However, after our system upgraded SonarQube Server from version 10.8.0 to 2025.1, the Build Wrapper started failing with the following error:
dyld: Symbol not found: __ZTTNSt3__114basic_ofstreamIcNS_11char_traitsIcEEEE
Referenced from: <path>/build-wrapper-macosx-x86
Expected in: /usr/lib/libc++.1.dylib
It was working fine on macOS 15, but after investigating, I discovered that the Build Wrapper was updated from 6.61 to 6.62. It appears that the new version is not compatible with macOS 11. However, according to the documentation, the minimum required macOS version is 10.14.3, which is confusing.
Expectation:
I need to analyze my C++ source code on macOS 11 with SonarQube Server 2025.1 (and future versions too).
Considering solutions:
Here are some possible solutions I’ve considered:
Upgrade to a newer macOS version
→ Not an option right now, as I have dependencies that require macOS 11.
Use an older Build Wrapper version
→ Based on what I’ve read, we must use the Build Wrapper version that ships with SonarQube Server.
Switch to Automatic Configuration mode (so Build Wrapper is no longer needed)
→ I found this approach in this documentation, but I’m unsure if it will work for my project or if there are any trade-offs.
Continue using Compilation Database mode and generate the compilation database with a third-party tool
→ This seems like a possible alternative, but it may require significant effort.
Question:
Are there any other possible solutions? And based on my constraints, what would be the best solution for my case?
p/s: I’m new to this domain, so if anything is incorrect or missing, please let me know, and I’ll provide more details.
The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.
Can you please clarify which architecture you’re using? Is it x86_64 or arm64?
→ It’s x86_64.
To check whether analysis works, Can you do an analysis using the automatic configuration mode and share the logs with us.
→ Do you just need to check if the analysis works on my environment? If so, can I analyse a dummy project to verify it? Otherwise, I’ll need to check with my team before sharing the logs.
Additionally, build-wrapper-macos-x86 version 6.61 and sonar-scanner-cli-5.0.1.3006-macosx are working fine on my environment
Yes analyzing dummy projects would be enough to check if analysis works using the same versions that caused the failures, so that should be build-wrapper-macos-x86 version 6.62
Not an option right now, as I have dependencies that require macOS 11.