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

   > This CI error seems to be occurring in every PR:
   > 
   > ```
   > Configuration/Tool: qemu-armv8a/rpproxy
   > 2026-01-20 04:31:48
   > 
------------------------------------------------------------------------------------
   >   Cleaning...
   > /github/workspace/sources/apps/Application.mk:238: target 
'signest.c.github.workspace.sources.apps.testing.ostest.o' given more than once 
in the same rule
   > /github/workspace/sources/apps/Application.mk:238: target 
'signest.c.github.workspace.sources.apps.testing.ostest.o' given more than once 
in the same rule
   >   Configuring...
   >   Building NuttX...
   > cu_main.c: In function 'sigint':
   > Error: cu_main.c:128:33: error: 'siginfo' undeclared (first use in this 
function)
   >   128 |   FAR struct cu_globals_s *cu = siginfo->si_user;
   >       |                                 ^~~~~~~
   > cu_main.c:128:33: note: each undeclared identifier is reported only once 
for each function it appears in
   > make[2]: *** [/github/workspace/sources/apps/Application.mk:330: 
cu_main.c.github.workspace.sources.apps.system.cu.o] Error 1
   > make[2]: Target 'all' not remade because of errors.
   > make[1]: *** [Makefile:54: /github/workspace/sources/apps/system/cu_all] 
Error 2
   > make[1]: Target 'all' not remade because of errors.
   > make: *** [tools/LibTargets.mk:248: 
/github/workspace/sources/apps/libapps.a] Error 2
   > make: Target 'all' not remade because of errors.
   > /github/workspace/sources/nuttx/tools/testbuild.sh: line 385: 
/github/workspace/sources/nuttx/../nuttx/nuttx.manifest: No such file or 
directory
   > ```
   
   it's strange why https://github.com/apache/nuttx-apps/pull/3314 pass ci. 


-- 
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