Forum Discussion

dncmrc's avatar
dncmrc
Icon for Occasional Contributor rankOccasional Contributor
5 years ago
Solved

nios2-elf-gcc.exe: error: CreateProcess: No such file or directory

Hi, Windows 10 Pro 2004 19041.450 Quartus Prime Pro 19.4, build 64 All Intel and Nios SW is on a local drive. I get this error in the NiosII shell: "nios2-elf-gcc.exe: error: CreateProc...
  • dncmrc's avatar
    dncmrc
    5 years ago

    As a solution to the issue nios2-elf-gcc.exe: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory we have found useful what follows.

    Before running make.exe on the generated Makefile, add this to your bash script:

    export WSLENV=PATH/l:${WSLENV}
    sed -i 's/\(adjust-path[-mixed]*\) = .*/\1 = $1/' Makefile

    WSLEN fixes missing pathnames, while sed basically removes the effect of adjust-path.

    This is an issue introduced by a Windows update but I still believe Intel should provide a fix or patch for it. We wasted several days on it.

Eliath_G_Intel's avatar
Eliath_G_Intel
Icon for Occasional Contributor rankOccasional Contributor
5 years ago

Hi Marco!

Thanks for reaching us,

Please follow the next steps:


  1. Install WSL
  2. Open the terminal
  3. run $ nios2_command_shell.sh
  4. run the tests you need to make , at this point it should work properly.


As resume, you need to have WSL correctly installed.

Please try those steps and let me know the results.


Best regards,

-Eliath Guzman


  • dncmrc's avatar
    dncmrc
    Icon for Occasional Contributor rankOccasional Contributor
    5 years ago

    Hi Eliath,

    I tried what you suggest and I got the same error.

    We have had WSL correctly installed from the very beginning. Please read my messages above. The issue started after the latest Windows 10 updates.

    Regards

    • Suri's avatar
      Suri
      Icon for New Contributor rankNew Contributor
      5 years ago

      Hello Intel support team,

      Is there any solution for this error?

      Me too getting the same error after updating the Windows. I tried to reinstall everything. But, getting same error. Please let me know the solution since it is very urgent.

  • billmax's avatar
    billmax
    Icon for Occasional Contributor rankOccasional Contributor
    5 years ago

    I have the same or similar problem.

    My wsl (v2) is up to date as is my Win10 version (2004). It appears the problem is paths.

    The $PATH in nios command shell contains

    /mnt/e/intelFPGA/20.1/nios2eds/bin/gnu/H-i686-pc-linux-gnu/bin

    That path doesn't exist in my installation: however this one does

    /mnt/e/intelFPGA/20.1/nios2eds/bin/gnu/H-x86_64-mingw32/bin

    Neither of those paths (or their windows equivalents) is in my windows path environment or subsequently in my wsl $PATH.

    Should the 20.1 quartus full install have added a path for nios2eds, and if so which?

    • SHard2's avatar
      SHard2
      Icon for Occasional Contributor rankOccasional Contributor
      5 years ago

      Hi

      I have exactly the same error. Is there any resolution to this?

      Regards

      Simon

      • Suri's avatar
        Suri
        Icon for New Contributor rankNew Contributor
        5 years ago

        As a temporary solution, I just found that it is working with normal windows command prompt instead of WSL. So, I just opened windows command prompt with "cmd" command. Then, set the path (that may vary on your system) as below.

        set PATH=C:\intelFPGA_pro\20.1\nios2eds\bin\gnu\H-x86_64-mingw32\bin;%PATH%

        And, built my library using "nios2-elf-gcc.exe" commands. Only thing, unix-style shell commands won't work. I just replaced "rm -f" with "del" in my makefile.

        ----

        Hope Intel will provide the proper solution to this very soon!!