> root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1 > make -C tools -f Makefile.host mkconfig.exe
> I also checked the tools directory and there is a mkconfig.exe When you build using Ubuntu for Windows 10 you get a *.exe file? The error is that tools/mkconfig is not found. This is how tools/Makefile.unix uses the mkconfig tool, tools/Makefile.win uses mkconfig.exe On Tue, Oct 13, 2020 at 10:11 PM Eduard Niesner <niesneredu...@gmail.com> wrote: > > 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' > > > .... > > > 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. > It seems like the mkconfig is created - maybe it looks for it in the wrong > place? > > Edi > > > On Tue, Oct 13, 2020 at 11:48 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > > > > /bin/sh: 1: tools/mkconfig: not found > > > tools/Makefile.unix:247: recipe for target 'include/nuttx/config.h' > > failed > > > make: *** [include/nuttx/config.h] Error 127 > > > > Your problem is not that kconfig-frontends is not being built, but > > rathter that tools/mkconfig is not being built. That should happen > > automatically when you build NuttX because it is required by the > > dependencies. If you use 'make V=1' you should have seen > > tools/mkconfig being built. There should also be a tools/mkconfig > > binary in your tools/directory. > > > > If not, then the make rule is broken somehow in your case. > > > > You can try building tools/mkconfig just as a test to see if that solves > > the build problem: make -C tools -f Makefile.host > > > > That is not a solution but is a good verification of the build failure. > > > > > >
