ECI release-eci_3.3 Build error

Xander3 · ‎01-15-2025

When I first attempted to build, it successfully completed. However, after I reran the ./setup.sh script and chose to start building with core-bullseye, an error occurred. I am using ECI version 3.3, with a system version of Debian 11 and a kernel version of 5.10.0-33-amd64. Could you please give me some hints on how to resolve this issue?

Peh_Intel · ‎01-16-2025

Hi Xander3,

This is a known limitation with ECI. When building ECI, the build process may fail due to do_fetch errors. These errors occur when the build engine is unable to reach external dependencies via the network. Most often, these errors occur due to network instability, broken mirrors, or proxy server instability.

I was able to reproduce the issue and had tried several attempts but still having the do_fetch errors. As such, I need to check with the development team regarding this matter.

In a meanwhile, you can try with another way installing ECI, which is to use packages provided with the ECI release.

Regards,

Peh

Xander3 · ‎01-16-2025

Thank you for your reply.I have tried the Install Packages method before, but the results tested using start-cyclic.py were poor. Is it possible to obtain the best results by using the Build ECI from Source and Install method to install ECI?

Wan_Intel · ‎01-27-2025

Hi Xander3,

Thanks for the information.

Do you use a proxy when you install the ECI? On the other hand, do you install the ECI on a fresh Operating system?

Regards,

Wan

Xander3 · ‎02-05-2025

I have already used a proxy and installed ECI on a fresh operating system.

Wan_Intel · ‎02-09-2025

Hi Xander,

Thanks for the information.

If you are behind a proxy, make sure that you set the following environment variables: HTTP_PROXY, HTTPS_PROXY, and NO_PROXY. On the other hand, could you please try from a network that does not require proxies?

Regards,

Wan

Wan_Intel · ‎02-13-2025

Hi Xander,

Thanks for the question.

This case will no longer be monitored since we have provided suggestion.

If you need additional information from Intel, please submit a new ticket.

Regards,

Wan