Forum Discussion
Noted. We shall close this thread.
Please post a response in the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you with your follow-up questions.
Hi
Before you guys create a patch, remember there are several issues, at least 3
1. Some of the building scripts is using uname-r to check the platform, this is where the big M and little m problem occur.
One example is nios2_command_shell.sh others are
2. Some scripts is not using uname -r but other ways to determinate the platform and they also get the problems with the M and m
Most notable is reading the /proc/version file, like some perl scripts which fails because of the M and m
One example is intelFPGA/20.1/nios2eds/bin/nios2-stackreport.pl
which use
open my $handle, "<", "/proc/version" || return;
my $first_line = <$handle>;
close $handle;
return ($first_line =~ /Microsoft/);
3. There is a hickup from the earlier used cygwin remains to the new wsl when it looks for "/bin/gnu/H-x86_64-pc-linux-gnu/bin" to create the build env variables.
4. Paths problem for gcc at the very bottom.
nios2-elf-gcc.exe: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory
gcc can not find the cc1 executable, it is not copied to the temporary build directory structure that is on the fly created when compiling nios.
Regards Stefan
- NikoR5 years ago
Occasional Contributor
Hi Intel.
Can you please give an update on the status on the UniPHY generate issue?
Are there patches available for the various Quartus releases starting from 19.1 that fix the issues?
Regards
Nikolay