xiaoxiang781216 commented on PR #10522:
URL: https://github.com/apache/nuttx/pull/10522#issuecomment-1710320909

   > @xiaoxiang781216 there are some issues in the MacOS building:
   > 
   > ```
   > Ignored files:
   >    include/netutils/cJSON.h
   >    include/netutils/cJSON_Utils.h
   >    netutils/cjson/cJSON/
   >    netutils/cjson/v1.7.10.tar.gz
   > 
   > nothing to commit, working tree clean
   >   Configuring...
   > make: *** [olddefconfig] Error 126
   >   Building NuttX...
   > clang: error: unknown argument '-mlongcalls'; did you mean '-mlong-calls'?
   > make[1]: *** No rule to make target `context'.
   > make: *** [libs/libm/.context] Error 2
   > /Users/runner/work/nuttx/nuttx/sources/apps/Application.mk:99: "program 
names  sh does not match mainsrcs 
nsh_main.c.Users.runner.work.nuttx.nuttx.sources.apps.system.nsh.o 
sh_main.c.Users.runner.work.nuttx.nuttx.sources.apps.system.nsh.o  "
   > /Users/runner/work/nuttx/nuttx/sources/apps/Application.mk:99: "program 
names  sh does not match mainsrcs 
nsh_main.c.Users.runner.work.nuttx.nuttx.sources.apps.system.nsh.o 
sh_main.c.Users.runner.work.nuttx.nuttx.sources.apps.system.nsh.o  "
   > make: Target `all' not remade because of errors.
   > /Users/runner/work/nuttx/nuttx/sources/nuttx/tools/testbuild.sh: line 370: 
/Users/runner/work/nuttx/nuttx/sources/nuttx/../nuttx/nuttx.manifest: No such 
file or directory
   >   Normalize esp32-devkitc/wifi
   > make: *** [olddefconfig] Error 126
   > make: *** [savedefconfig] Error 126
   > make: *** [olddefconfig] Error 126
   > HEAD detached at pull/10522/merge
   > Untracked files:
   >    kwarning
   > 
   > nothing added to commit but untracked files present
   > 
   
   yes, macOS ci fail recently, but I don't find the patch causes this fail.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to