Cannot build H7 configuration using Ubuntu for Windows 10
Hi all, I am getting some build issues when I try to build nucleo-h743zi configuration using Ubuntu for Windows 10. I used to execute the following commands in order to build Nuttx. But starting Nuttx 9.1 I am getting the following error. This is also reproducible on the current master. 1. make distclean 2. ./tools/configure.sh -u nucleo-h743zi:nsh 3. make #3 generates this error: /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 root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# Does anybody have any idea where this error is coming from? Also, if instead of #2 I configure it for Linux (replaced -u with -l) ./tools/configure.sh *-l* nucleo-h743zi:nsh the build works fine but the .bin does not run on my board (it crashes right at the beginning). Any help is appreciated. Edi
Re: Cannot build H7 configuration using Ubuntu for Windows 10
On Tue, Oct 13, 2020, 9:08 AM Eduard Niesner wrote: > Hi all, > > I am getting some build issues when I try to build nucleo-h743zi > configuration using Ubuntu for Windows 10. > > I used to execute the following commands in order to build Nuttx. But > starting Nuttx 9.1 I am getting the following error. This is also > reproducible on the current master. > >1. make distclean >2. ./tools/configure.sh -u nucleo-h743zi:nsh >3. make > > #3 generates this error: > /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 > root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# > You are missing the kconfig frontends See the note here https://nuttx.apache.org/docs/latest/quickstart/install.html If there is something not clear please let us know we have recently made large changes to improve the docs so certainly want to continue to improve them. --Brennan >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
Thank you for your suggestion. I already had kconfig-frontends installed because the build works with no issues on older versions of Nuttx (tag 8.1 and tag 9.0 for example). It stopped working on tag 9.1. I tried to reinstall kconfig-frontends using the link you provided and I run the three steps from my previous email again to build (by the way - the documentation was clear and easy to follow). I got the same error. /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 Any other suggestions? Edi On Tue, Oct 13, 2020 at 7:14 PM Brennan Ashton wrote: > On Tue, Oct 13, 2020, 9:08 AM Eduard Niesner > wrote: > > > Hi all, > > > > I am getting some build issues when I try to build nucleo-h743zi > > configuration using Ubuntu for Windows 10. > > > > I used to execute the following commands in order to build Nuttx. But > > starting Nuttx 9.1 I am getting the following error. This is also > > reproducible on the current master. > > > >1. make distclean > >2. ./tools/configure.sh -u nucleo-h743zi:nsh > >3. make > > > > #3 generates this error: > > /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 > > root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# > > > > You are missing the kconfig frontends > > See the note here > https://nuttx.apache.org/docs/latest/quickstart/install.html > > If there is something not clear please let us know we have recently made > large changes to improve the docs so certainly want to continue to improve > them. > > --Brennan > > > >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
/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.
Re: Cannot build H7 configuration using Ubuntu for Windows 10
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 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. > > >
Re: [DISCUSS] NuttX 10.0.0 Release schedule
Hi, I backported all the PRs that were labeled for backporting. If anyone can take a look and merge them that would be great. I created the Release Notes-10.0 board and added some cards there. The "Minor" column regroups all of the style, typos, grammar like PRs. Is there a way to automatically add all the remaining cards to the To-Add column? BTW, I'm using this "merged:>2020-07-23" to filter PRs. Speaking of automation, I see Github project's have options to automatically add newly merged PRs to boards. This can help a lot, especially if there is a way to add PRs to different columns depending on labels. Did anyone use that before? If that's usable we can create the 10.1 Project now. Also, we finished working on the old 9.1 Project, it should be close, right? On Sat, Oct 10, 2020 at 10:49 AM Abdelatif Guettouche wrote: > > > I did notice a fair number of patches for bug fixes this week that we may > > want to be applying to this release including the spresense and esp, but > > there may have been others as well. It would be nice if those could be > > backported as needed prior to cutting the RC. > > Regarding Xtensa/ESP32, I can backport a couple, but it's better to > leave those that add new features for the next release. > > > On Sat, Oct 10, 2020 at 3:09 AM Brennan Ashton > wrote: > > > > I'm a little behind where I wanted to be but I have collected a bunch of > > the boards that we support and am going to work through what I can test > > with them this weekend. > > > > I did notice a fair number of patches for bug fixes this week that we may > > want to be applying to this release including the spresense and esp, but > > there may have been others as well. It would be nice if those could be > > backported as needed prior to cutting the RC. > > > > --Brennan > > > > On Sat, Oct 3, 2020, 9:52 PM Brennan Ashton > > wrote: > > > > > The releases/10.0 branches have been created off of master for both > > > apps and the OS. > > > > > > I will work on populating the release note board tomorrow and starting > > > to compile them. > > > If any fixes need to be made for the 10.0.0 release they should be > > > made against master > > > and then a new PR made against the release branch with BACKPORT in the > > > title so it > > > is easier to identify. > > > > > > Also this issue was called out as being a blocker: > > > https://github.com/apache/incubator-nuttx/issues/1804 > > > > > > --Brennan > > > > > > On Tue, Sep 22, 2020 at 10:13 PM Brennan Ashton > > > wrote: > > > > > > > > Hey all, we have talked in loose terms about this release, but I think > > > > it is time we committed, it has been probably too long since our last > > > > release. > > > > > > > > Here is what I would propose for a release schedule: > > > > > > > > 09/28/20 -- Master Stability Window (keep the merging of risky PRs > > > > to a minimum this week) > > > > 10/03/20 -- Create the 10.0 release branch > > > > 10/04/20 - 10/12/20 -- Stabilize / test / release notes > > > > Additionally in this window we need to make a couple CI tweeks to > > > > handle the new docs off of the release branch (I expect this won't be > > > > much work, but will be easier with the branch in place) > > > > 10/12/20 -- Tag RC0 and call for PPMC / Community Vote > > > > 10/15/20 (or when we have the votes) Call for IPMC Vote or create a > > > > new RC if needed to address issues > > > > 10/23/20 (Pending votes and RC0 issues) -- Release RC0 > > > > 10/24/20 -- Update site and announce (we have to wait for download > > > > mirrors to sync). > > > > > > > > I know that is almost a month, but that is usually about how long it > > > > takes for the whole process, but realistically there is only a week or > > > > so where we are aiming to slow down and stabilize the master branch. > > > > The rest of it is testing, documenting, voting, and waiting time. > > > > > > > > I can be the release manager again for this one. But it would be great > > > > if someone else jumps in for the release after and I will try to > > > > document things a bit more to make the process easier. We will need > > > > to have more than one release manage to graduate, there are other > > > > projects that have run into this. > > > > > > > > --Brennan > > >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
> 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 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 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. > > > > > >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
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
Re: Cannot build H7 configuration using Ubuntu for Windows 10
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.
Re: [DISCUSS] NuttX 10.0.0 Release schedule
On Tue, Oct 13, 2020, 2:12 PM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote: > Hi, > > I backported all the PRs that were labeled for backporting. If anyone > can take a look and merge them that would be great. > I created the Release Notes-10.0 board and added some cards there. > The "Minor" column regroups all of the style, typos, grammar like PRs. > Is there a way to automatically add all the remaining cards to the > To-Add column? BTW, I'm using this "merged:>2020-07-23" to filter > PRs. > > Speaking of automation, I see Github project's have options to > automatically add newly merged PRs to boards. This can help a lot, > especially if there is a way to add PRs to different columns depending > on labels. Did anyone use that before? If that's usable we can > create the 10.1 Project now. > Also, we finished working on the old 9.1 Project, it should be close, > right? > Ah. I actually was finishing up scripting to manage this and was going to generate it tonight. It is also capable of syncing the lists and generating new boards and letting you see the PR body while you write the release not entry. There are like 600 for this release and I wanted a better way. The auto add feature is actually very minimal and cannot acomplish this, I tried it for the last release. --Brennan >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
Yeah, there is definitely something wrong - I just tried again (ubuntu for windows 10). 1. Cleaned everything (git clean and make distclean) 2. checked that the *mkconfig.exe* or any other *mkconfig *binary does not exist in the tools folder 3. called './tools/configure.sh -u nucleo-h743zi:nsh' 4. called 'make' 5. mkconfig*.exe *showed up in the tools folder. I even tried to make fresh clones of nuttx and apps and run the above steps again. I am not sure what else I could try.. Edi On Wed, Oct 14, 2020 at 12:29 AM Gregory Nutt 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' > > 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 > >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
It looks like the extension got messed up. If that's the case renaming mkconfig.exe to mkconfig should at least build. On Tue, Oct 13, 2020 at 10:45 PM Eduard Niesner wrote: > > Yeah, there is definitely something wrong - I just tried again (ubuntu for > windows 10). > >1. Cleaned everything (git clean and make distclean) >2. checked that the *mkconfig.exe* or any other *mkconfig *binary does >not exist in the tools folder >3. called './tools/configure.sh -u nucleo-h743zi:nsh' >4. called 'make' >5. mkconfig*.exe *showed up in the tools folder. > > I even tried to make fresh clones of nuttx and apps and run the above steps > again. > I am not sure what else I could try.. > > Edi > > On Wed, Oct 14, 2020 at 12:29 AM Gregory Nutt 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' > > > > 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 > > > >
Re: [DISCUSS] NuttX 10.0.0 Release schedule
> Ah. I actually was finishing up scripting to manage this and was going to > generate it tonight. It is also capable of syncing the lists and generating > new boards and letting you see the PR body while you write the release not > entry. There are like 600 for this release and I wanted a better way. Ah okay, good! Feel free to delete the Project I just created then. We will use your script once finished. On Tue, Oct 13, 2020 at 10:42 PM Brennan Ashton wrote: > On Tue, Oct 13, 2020, 2:12 PM Abdelatif Guettouche < > abdelatif.guettou...@gmail.com> wrote: > > > Hi, > > > > I backported all the PRs that were labeled for backporting. If anyone > > can take a look and merge them that would be great. > > I created the Release Notes-10.0 board and added some cards there. > > The "Minor" column regroups all of the style, typos, grammar like PRs. > > Is there a way to automatically add all the remaining cards to the > > To-Add column? BTW, I'm using this "merged:>2020-07-23" to filter > > PRs. > > > > Speaking of automation, I see Github project's have options to > > automatically add newly merged PRs to boards. This can help a lot, > > especially if there is a way to add PRs to different columns depending > > on labels. Did anyone use that before? If that's usable we can > > create the 10.1 Project now. > > Also, we finished working on the old 9.1 Project, it should be close, > > right? > > > > Ah. I actually was finishing up scripting to manage this and was going to > generate it tonight. It is also capable of syncing the lists and generating > new boards and letting you see the PR body while you write the release not > entry. There are like 600 for this release and I wanted a better way. > > The auto add feature is actually very minimal and cannot acomplish this, I > tried it for the last release. > > --Brennan > > > >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
It looks like the extension got messed up. If that's the case renaming mkconfig.exe to mkconfig should at least build. Either that, or configure.sh and/or sethost.sh set up for the wrong host. When you select Ubuntu with the -u option, sethost.sh should set the host to Windows, but the environment to Ubuntu. After running configure.sh, can you please check the resulting .config file? What is the HOST? What is the environment. Even if those are correct, there could be something else wrong in the armv7-m/Kconfig or Toolchain.defs that using the wrong settings. There are lots of possbilities.
Re: Cannot build H7 configuration using Ubuntu for Windows 10
Yes, renaming the mkconfig*.exe* to mkconfig did the trick. I had the same problem with mkversion*.exe* - renamed it to mkversion and the build worked fine. If I get some time tomorrow, I will try to find the commit that messed up the extension. Thanks! On Wed, Oct 14, 2020 at 12:50 AM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote: > It looks like the extension got messed up. If that's the case > renaming mkconfig.exe to mkconfig should at least build. > > On Tue, Oct 13, 2020 at 10:45 PM Eduard Niesner > wrote: > > > > Yeah, there is definitely something wrong - I just tried again (ubuntu > for > > windows 10). > > > >1. Cleaned everything (git clean and make distclean) > >2. checked that the *mkconfig.exe* or any other *mkconfig *binary does > >not exist in the tools folder > >3. called './tools/configure.sh -u nucleo-h743zi:nsh' > >4. called 'make' > >5. mkconfig*.exe *showed up in the tools folder. > > > > I even tried to make fresh clones of nuttx and apps and run the above > steps > > again. > > I am not sure what else I could try.. > > > > Edi > > > > On Wed, Oct 14, 2020 at 12:29 AM Gregory Nutt > 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' > > > > > > 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 > > > > > > >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
Yes, renaming the mkconfig*.exe* to mkconfig did the trick. I had the same problem with mkversion*.exe* - renamed it to mkversion and the build worked fine. If I get some time tomorrow, I will try to find the commit that messed up the extension. Got it! Okay, this was easy once you know it is only the HOSTEXEXT that is screwed up. That is defined in tools/Config.mk and the definition there in WRONG! 116 ifeq ($(CONFIG_HOST_WINDOWS),y) 117 HOSTEXEEXT ?= .exe 118 endif When Ubuntu it selects CONFIG_HOST_WINDOWS=y but the HOSTEXEEXT should be an empty string, not .exe. That is the root cause of the problem. This is commit 567962bd626 introduced the error commit 567962bd6263bf8809fb63c739f6ec668c69c416 Author: Xiang Xiao Date: Tue May 19 18:29:28 2020 +0800 build: Move the extension definition to common place Signed-off-by: Xiang Xiao This should be fixed in the 10.0 release. I will open an issue. Thanks for your patience in getting to the bottom of this, Ed, Greg
Re: Cannot build H7 configuration using Ubuntu for Windows 10
I am glad that you found the issue. Thanks for your patience and support! Edi On Wed, Oct 14, 2020 at 1:15 AM Gregory Nutt wrote: > > > Yes, renaming the mkconfig*.exe* to mkconfig did the trick. > > I had the same problem with mkversion*.exe* - renamed it to mkversion and > > the build worked fine. > > > > If I get some time tomorrow, I will try to find the commit that messed up > > the extension. > > Got it! Okay, this was easy once you know it is only the HOSTEXEXT that > is screwed up. That is defined in tools/Config.mk and the definition > there in WRONG! > > 116 ifeq ($(CONFIG_HOST_WINDOWS),y) > 117 HOSTEXEEXT ?= .exe > 118 endif > > When Ubuntu it selects CONFIG_HOST_WINDOWS=y but the HOSTEXEEXT should > be an empty string, not .exe. That is the root cause of the problem. > > This is commit 567962bd626 introduced the error > > commit 567962bd6263bf8809fb63c739f6ec668c69c416 > Author: Xiang Xiao > Date: Tue May 19 18:29:28 2020 +0800 > > build: Move the extension definition to common place > > Signed-off-by: Xiang Xiao > > This should be fixed in the 10.0 release. I will open an issue. > > Thanks for your patience in getting to the bottom of this, Ed, > > Greg > > > > >
Re: Cannot build H7 configuration using Ubuntu for Windows 10
I created issue: https://github.com/apache/incubator-nuttx/issues/1985 On 10/13/2020 4:15 PM, Gregory Nutt wrote: Yes, renaming the mkconfig*.exe* to mkconfig did the trick. I had the same problem with mkversion*.exe* - renamed it to mkversion and the build worked fine. If I get some time tomorrow, I will try to find the commit that messed up the extension. Got it! Okay, this was easy once you know it is only the HOSTEXEXT that is screwed up. That is defined in tools/Config.mk and the definition there in WRONG! 116 ifeq ($(CONFIG_HOST_WINDOWS),y) 117 HOSTEXEEXT ?= .exe 118 endif When Ubuntu it selects CONFIG_HOST_WINDOWS=y but the HOSTEXEEXT should be an empty string, not .exe. That is the root cause of the problem. This is commit 567962bd626 introduced the error commit 567962bd6263bf8809fb63c739f6ec668c69c416 Author: Xiang Xiao Date: Tue May 19 18:29:28 2020 +0800 build: Move the extension definition to common place Signed-off-by: Xiang Xiao This should be fixed in the 10.0 release. I will open an issue. Thanks for your patience in getting to the bottom of this, Ed, Greg
Re: Cannot build H7 configuration using Ubuntu for Windows 10
The fix is here: https://github.com/apache/incubator-nuttx/pull/1986 But Edi, can you boot the image built with -u option? I don't think there is any real difference between -u option and -l option in Ubuntu On Windows. If the image built with -l can't work, the image with -u should not work too. On Wed, Oct 14, 2020 at 6:24 AM Gregory Nutt wrote: > I created issue: https://github.com/apache/incubator-nuttx/issues/1985 > > On 10/13/2020 4:15 PM, Gregory Nutt wrote: > > > >> Yes, renaming the mkconfig*.exe* to mkconfig did the trick. > >> I had the same problem with mkversion*.exe* - renamed it to mkversion > and > >> the build worked fine. > >> > >> If I get some time tomorrow, I will try to find the commit that messed > up > >> the extension. > > > > Got it! Okay, this was easy once you know it is only the HOSTEXEXT > > that is screwed up. That is defined in tools/Config.mk and the > > definition there in WRONG! > > > > 116 ifeq ($(CONFIG_HOST_WINDOWS),y) > > 117 HOSTEXEEXT ?= .exe > > 118 endif > > > > When Ubuntu it selects CONFIG_HOST_WINDOWS=y but the HOSTEXEEXT should > > be an empty string, not .exe. That is the root cause of the problem. > > > > This is commit 567962bd626 introduced the error > > > > commit 567962bd6263bf8809fb63c739f6ec668c69c416 > > Author: Xiang Xiao > > Date: Tue May 19 18:29:28 2020 +0800 > > > > build: Move the extension definition to common place > > > > Signed-off-by: Xiang Xiao > > > > This should be fixed in the 10.0 release. I will open an issue. > > > > Thanks for your patience in getting to the bottom of this, Ed, > > > > Greg > > > > > > > > > >
