I used 'make V=1' and I saw that mkconfig is being built successfully.
root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1
make -C tools -f Makefile.host mkconfig.exe
make[1]: Entering directory
'/mnt/d/Work/Development/Git/GitHub/nuttx/tools'
No, the binary tools/mkconfig is NOT being built. Instead,
tools/mkconfig.exe is being built. That will not work on Ubuntu for
windows. There is something screwed up in your configuration.
Specifically EXEEXT must be .exe??? But that should not happen unless
you are actually trying to build for Windows Cygwin or MSYS.
I also checked the tools directory and there is a mkconfig.exe that was
created about the same time when I called make v=1.
Again that is wrong. It is expecting tools/mkconfig, and NOT
tools/mkconfig.exe
This is still probably a error in some commit. It would be a kindness
if you could do the bisect between 9.0 and 9.1 to identify the offending
commit. My guess is that something was broken in tools/configure.sh or
in tools/sethost.sh
In principle, there is no real difference between Ubuntu for Windows and
Linux, so if you were to configure for Linux:
./tools/configure.sh -1 nucleo-h743zi:nsh
That should work too.
