'Ignore unknown compiler' with WindRiver GCC

SonarQube Server / Community Build
1

Tool versions:

  • SonarQube Server Enterprise Edition v10.7 (96327)
  • sonar-scanner-cli-6.2.1.4610-linux-x64 deployed using zip

The goal:

Scan a project that uses the following WindRiver compiler version:

$ /opt/WindRiver/WB_PID_3_9_13/gnu/4.3.3-vxworks-6.9/x86-linux2/bin/c++arm --version
c++arm (Wind River VxWorks G++ 4.3-386) 4.3.3

In documentation CFamily Prerequisites, the Supported compilers does state that “Wind River Diab and GCC compilers” are supported.

I know the GCC version is quite outdated, but any confirmation whether this version is supported or not would be appreciated.

The problem

INFO Ignore unknown compiler: …/WindRiver/gnu/4.3.3-vxworks-6.9/x86-linux2/bin/c++arm

2

I was able to workaround the problem by textually replacing the c++arm with another (apparently supported) compiler, in the compile_commands.json.

I am still interested in the original question though, whether the “4.3.3-vxworks-6.9” toolchain is supported or not.

4

Hello @mletavk, and thanks for sharing the issue with us.

I would expect c++arm to be supported after CPP-5154. The fix for the ticket was released in CFamily analyzer version 6.60, which is now available on SonarQube cloud and on SonarQube server starting in version 10.8.

Would it be possible for you to try analysis with a newer version of SonarQube server or with SonarQube cloud?

Best regards,
Michael

5

Hello Michael!

Unfortunately both my company’s test and production environments are at 10.7 and I won’t be able to verify myself, so I’ll trust you. When we adopt new version and in case the issue persists, I’ll just create a new ticket.

Thanks for the information!

1 Like
7

Is the warning just informational, or will it actually prevent issues from being logged in files that are using that compiler?

Specifically, would we expect new issues to get logged after upgrading from 10.7 to 10.8, because now the compiler is supported?

8

It impacts issues; Translation units that are using this compiler are skipped. There should be another log message which provides the number of such translation units:

INFO  Number of skipped unsupported compilation units: N

I would expect that, yes.

9

Thank you! That’s really helpful, especially now that I know to look for that INFO message about unsupported compilation units.

I’ll work with our IT team to upgrade to a newer version. (I’m working with Michal on the same project at my company)

2 Likes
10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.