simbit18 commented on PR #3263:
URL: https://github.com/apache/nuttx-apps/pull/3263#issuecomment-3682348507

   @acassis @wangchen61698  This error is also present.
   
   ```
   
====================================================================================
   Configuration/Tool: qemu-intel64/jumbo
   2025-12-22 14:28:31
   
------------------------------------------------------------------------------------
     Cleaning...
     Configuring...
     Building NuttX...
     % Total    % Received % Xferd  Average Speed   Time    Time     Time  
Current
                                    Dload  Upload   Total   Spent    Left  Speed
   
     0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
     0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
   
   100  496k  100  496k    0     0  2884k      0 --:--:-- --:--:-- --:--:-- 
2884k
   ping.c: In function 'ping_main':
   Error: ping.c:293:7: error: 'struct ping_info_s' has no member named 
'devname'
     293 |   info.devname   = NULL;
         |       ^
   make[2]: *** [/github/workspace/sources/apps/Application.mk:330: 
ping.c.github.workspace.sources.apps.system.ping.o] Error 1
   make[2]: Target 'all' not remade because of errors.
   make[1]: *** [Makefile:54: /github/workspace/sources/apps/system/ping_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
     [1/1] Normalize qemu-intel64/jumbo
   
====================================================================================
   ```


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