Forum Discussion
Occasional Contributornios2-elf-gcc.exe: error: CreateProcess: No such file or directory
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/' MakefileWSLEN 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.
Occasional ContributorMy workaround is a combination of things.
I manually added a couple of sdk paths to my windows environment Path. (E:\intelFPGA\20.1\nios2eds\bin;E:\intelFPGA\20.1\nios2eds\bin\gnu\H-x86_64-mingw32\bin)
I rebooted wsl (by restarting LxssManager service) to get the updated $PATH.
I edited the Makefile to change "Microsoft" to "microsoft"
Occasional ContributorAdditional details to workarounds/corrections
There are problems trying to create a new app or create a new format Makefile for an older app.
I had to manually create a wsl env for SOPC_KIT_NIOS2. In wsl:
export SOPC_KIT_NIOS2=/mnt/e/intelFPGA/20.1/nios2eds
Then for any create-this-app change "Microsoft" to "microsoft"
Then edit the resulting created Makefile to change "Microsoft" to "microsoft"
and change
APP_LDFLAGS += -msys-lib=$(call adjust-path-mixed,$(SYS_LIB))
to
APP_LDFLAGS += -msys-lib=hal_bsp
additional:
change Makefile to
BUILD_PRE_PROCESS := touch $(ELF).srec
(per this post )
modify nios2-download and nios2-configure-sof scripts to use lower-case 'm'
dncmrcAs 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/' MakefileWSLEN 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.
