ccache: FATAL: Could not find compiler "C:\Nordic\v1.8.0\toolchain\opt\bin\arm-none-eabi-gcc.exe" in PATH

[Gwen Stouthuysen]

I'm faced with a special error: we are not able to install the nRF Connect V1.8.0 using the tools published by Nordic.

We use the latest version of the tool chain manager and this claims to be successful

When attempting to build a blinky example for the nRF9160DK using SES we stumble upon the PATH not being correctly set for the compiler.

We tried to add the PATH manually, but this does not solve the issue.

We use this in an IoT oriented education, where we see this with one Windows 10 station, the other students have no problems.

The specific computer is not managed by a corporation, it is a personal laptop. I tried to replicate the issue, but was not successful.

[Øyvind]

Hello, 

Does the file C:\Nordic\v1.8.0\toolchain\opt\bin\arm-none-eabi-gcc.exe actually exist?

Can you provide more details from how you are opening the Blinky sample in SES? Are you choosing correct Toolchain Path? What path is configured under Tools -> Options -> nRF Connect ?

Kind regards,
Øyvind

[Gwen Stouthuysen]

The config screen:

Project loads normal

Then fails at Build Solution.

[Øyvind]

Hello, 

1. Can you please provide the build output log from SES? 
2. Have you verified that C:\Nordic\v1.8.0\toolchain\opt\bin\arm-none-eabi-gcc.exe actually exists?
3. Have you tried to install the toolchain on another network? I.e. make sure that nothing is blocking the download.

Kind regards,
Øyvind

[Gwen Stouthuysen]

We verified the files where there and retried the installation several times.

We will look into the issue together this evening, from a network that is direct internet connected.

Is there a way that we can let you look into the issue?

I will collect compiler output, and try to use VS code and verify anything different might happen.

[Øyvind]

Do you have ccache installed on that computer? Could there be a path issue between the toolchain and ccache?

Gwen Stouthuysen said:

We will look into the issue together this evening, from a network that is direct internet connected.

Yes, please do. 

Gwen Stouthuysen said:

I will collect compiler output, and try to use VS code and verify anything different might happen.

Sounds like a good plan. Building either via VS code, or via command prompt using west, can be good to verify the environment.