Kkula
Browse Questions » IOT2020 / IOT2040: Build Fault Intended For the Example Software

About User

Siemens Self Support

Questions Asked: 37.9K

Answers Given: 32

Statistics

Tags

0
  • Open
Siemens Self Support
Asked:18 Oct 2025

IOT2020 / IOT2040: Build Fault Intended For the Example Software

Dear,
 i try to build an example applications according to the instruction. Unfortunately, i failed. Anyone can help me, thank you in advance.
Below is the error hint:
12:47:49 **** Incremental Build of configuration IOT2000 Release for project HelloWorld ****
Info: Internal Builder is used for build
i586-poky-linux-g++ "-IC:\\00_Data\\SDK_Destination_Folder\\sysroots\\i586-nlp-32-poky-linux\\usr\\include" "-IC:\\00_Data\\SDK_Destination_Folder\\sysroots\\i586-nlp-32-poky-linux\\usr\\include\\c++\\5.3.0" "-IC:\\00_Data\\SDK_Destination_Folder\\sysroots\\i586-nlp-32-poky-linux\\usr\\include\\c++\\5.3.0\\i586-poky-linux" "-IC:\\00_Data\\SDK_Destination_Folder\\sysroots\\i586-nlp-32-poky-linux\\usr\\include\\mraa" "-IC:\\00_Data\\SDK_Destination_Folder\\sysroots\\i586-nlp-32-poky-linux\\usr\\include\\upm" "-IC:\\00_Data\\SDK_Destination_Folder\\sysroots\\i586-nlp-32-poky-linux\\usr\\include\\upm" -O0 -g3 -Wall -c -fmessage-length=0 -m32 -march=i586 -c -ffunction-sections -fdata-sections "--sysroot=C:\\00_Data\\SDK_Destination_Folder\\sysroots\\i586-nlp-32-poky-linux" -o example.o "..\\example.cpp"
i586-poky-linux-g++: error: CreateProcess: No such file or directory
12:47:50 Build Finished (took 1s.227ms)

#sosflex #IOT2020 / IOT2040 #siemens
2Answers 3Views 0Votes
0 Likes 0 Favourites 0 Followers 0 Comments
Answers(2)
Siemens Test Added an Answer on18 Oct 2025

Error during HelloWorld example build on IOT2000

Dear User,

The error "i586-poky-linux-g++: error: CreateProcess: No such file or directory" indicates that the compiler (i586-poky-linux-g++) is not found in your system's PATH environment variable, or the specified path is incorrect.

Here are potential solutions:

  • Verify SDK Installation: Ensure the IOT2000 SDK is correctly installed and the environment variables are properly set.
  • Check PATH Variable: Confirm that the directory containing i586-poky-linux-g++ (likely within your SDK's toolchain) is included in your system's PATH environment variable.
  • Rebuild Environment: Try rebuilding the development environment within your IDE (if applicable) or using the SDK's setup scripts.
  • Incorrect SDK Destination: Double check that the SDK_Destination_Folder variable is set correctly to your actual SDK installation location.

For detailed troubleshooting steps, refer to the following resources in SiePortal:

If you continue to experience issues, please provide the following information for further assistance:

  • Your operating system.
  • The exact SDK version you are using.
  • The contents of your PATH environment variable.

Sincerely,
Siemens Self Support

0
Siemens Test Added an Answer on18 Oct 2025
IoT2000 SDK Build Error - Node-Red

IoT2000 SDK Build Error - Node-Red

The error you're encountering during the SDK build for the IoT2000 likely stems from a failure to fetch the node-red package via npm. Specifically, the error message "Unable to establish SSL connection" indicates an issue with secure communication with the npm registry.

Here's a breakdown of the problem and potential solutions:

Possible Causes:

  • SSL Certificate Issues: Your system might not trust the SSL certificate used by the npm registry.
  • Network Connectivity: There may be network issues preventing access to the npm registry.
  • Proxy Configuration: If you are behind a proxy, it might not be configured correctly for npm.

Solutions:

  1. Update npm and Node.js: Ensure you have the latest versions of npm and Node.js installed on your Ubuntu system.
  2. Disable SSL Verification (Temporary): As a temporary workaround (not recommended for production), you can try disabling SSL verification for npm:

    npm config set strict-ssl false

  3. Configure Proxy Settings: If you are behind a proxy, configure npm to use it:

    npm config set proxy http://your-proxy-address:port

    npm config set https-proxy http://your-proxy-address:port

  4. Check Network Connectivity: Verify that your system can access the internet and specifically reach https://registry.npmjs.org.
  5. Clean Build Environment: Try cleaning the build environment and starting the build process from scratch.

For further assistance, please refer to the Siemens Support documentation and the meta-iot2000 GitHub repository for updated information.

0