|Anonymous | Login | Signup for a new account||2021-05-11 10:28 UTC|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000727||Taste||[All Projects] Orchestrator||public||2017-12-13 13:49||2018-06-13 15:34|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
Compile option -std=c99 set by the orchestrator
The Orchestrator enforces the usage of the C99 standard in user code, adding the flag -std=c99 to the compile command. This may prevent using third-party libraries that rely on newer versions of the standard or on compiler-specific features, as their include files may contain features not supported with that compiler option.
The choice of language version should be left to the user, and not imposed by the tool. The necessary compiler options can be added using the mechanism of TASTE directives.
|Tags||No tags attached.|
Have you tried to remove -std=c99 and does everything build as expected on your side?
I didn't try to remove the option.
This is not causing any issues for our build (apart from the escaping of '='). We need a modern version of c++ for some libraries, but this doesn't conflict with this flag: gcc takes both options -std=c99 and -std=c++11 at the same time, and uses the one passed last (c++11).
Nevertheless, this is just lucky: gcc retains the last option passed (c++11), and TASTE builds the compilation command in the right order (gcc ...
If this changes in the future, it might cause problems. I'd recommend not enforcing the -std=c99 option, but in any case it's not an issue for our usage of the tool.
|2017-12-13 13:49||miguel_munoz||New Issue|
new => assigned
|2017-12-13 13:49||miguel_munoz||Assigned To||
assigned => acknowledged
|2018-06-13 14:30||maxime||Note Added: 0003372|
|2018-06-13 15:34||miguel_munoz||Note Added: 0003374|
|Copyright © 2000 - 2011 MantisBT Group|