error in /usr/include/c++/7.3.0/arm-oe-linux-gnueabi/bits/os_defines.h

[AntonioSanta]

Please use the following bug reporting template to help produce actionable and reproducible issues:

• A brief description
  get errors on include files included automatically by Visual studio

• Expected results
  should compile as with an older version of Visual studio it compiles and works correctly
  or at least should allow change the versions of includes 7.3.0 to something else.

• Actual results (with build output window contents if applicable)
  1>/usr/include/c++/7.3.0/arm-oe-linux-gnueabi/bits/os_defines.h(44,19): error : missing binary operator before token "("
  and other errors like this.

• VC++ version, Linux system name and version, GCC/GDB/gdbserver version, CPU arch, etc. If you are using a specific version of Linux on an embedded board, we might need to know about it to get a repro on similar hardware
  Microsoft Visual Studio Community 2017
  Version 15.9.0
  VisualStudio.15.Release/15.9.0+28307.53
  Microsoft .NET Framework
  Version 4.7.03056

Installed Version: Community

Visual C++ 2017 00369-60000-00001-AA496
Microsoft Visual C++ 2017

ASP.NET and Web Tools 2017 15.9.04012.0
ASP.NET and Web Tools 2017

C# Tools 2.10.0-beta2-63501-03+b9fb1610c87cccc8ceb74a770dba261a58e39c4a
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

JavaScript Language Service 2.0
JavaScript Language Service

Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual C++ Wizards 1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package

MLGen Package Extension 1.0
MLGen Package Visual Studio Extension Detailed Info

ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

Visual Basic Tools 2.10.0-beta2-63501-03+b9fb1610c87cccc8ceb74a770dba261a58e39c4a
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual C++ for Linux Development 1.0.9.28218
Visual C++ for Linux Development

Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Tools for CMake 1.0
Visual Studio Tools for CMake

target is ARM 32 bit, compiler is g++

• Steps required to reproduce the error

• Required packages and commands to install

See our contributing instructions for assistance.

[itodirel]

we are aware of this issue and working on a fix, but the fix might take a while because of the complexity of the fix

[itodirel]

We believe this issue has been addressed. Please open a separate issue on the Developer Community if you are encountering or having further issues.

We have retired this issue list, here on Github. We now adopted and are using the Developer Community (https://developercommunity.visualstudio.com/spaces/62/index.html), for Cross Plat and Linux experiences (and C++ generally), which we are actively monitoring. Please use the Developer Community, to report issues or suggestions for bugs or new experiences. Further discussions on this thread here on Github might be unmonitored. If there is further comments or context to this current issue, please create a new issue on the Developer Community, and provide the context there. For any existing issues, which we can or able to reproduce, or for anything that is actionable to us and understood, we will provide an update right here in this thread. Additionally, for new suggestions or new issues, which at this time are in our roadmap, or for which we believe and have evidence that broadly and/or significantly benefit everyone, we will open a suggestion ticket, and link it here. For anything else, we recommend to please open a ticket on the Developer Community. That isn't because we will not look at the problem, or not investigate it otherwise, but simply because we need additional information. And for features, we are tracking them on the Developer Community.