gneworld commented on PR #2595:
URL: https://github.com/apache/nuttx-apps/pull/2595#issuecomment-2365403497

   > What about macOS and xtensa build errors?
   
   @cederom 
   
     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  340k  100  340k    0     0  1179k      0 --:--:-- --:--:-- --:--:-- 
1179k
   fatal: unable to access 'https://github.com/espressif/esp-phy-lib.git/': 
gnutls_handshake() failed: Error in the pull function.
   fatal: Fetched in submodule path 'components/esp_phy/lib', but it did not 
contain 06e7625de197bc12797dd701d6762229bca01826. Direct fetching of that 
commit failed.
   fatal: 
   make[1]: *** [chip/Make.defs:269: context] Error 128
   make: *** [tools/Unix.mk:457: arch/xtensa/src/.context] 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
     Normalize esp32s3-korvo-2/audio
   
====================================================================================
   Configuration/Tool: esp32s3-meadow/usbnsh
   
   @cederom 
   
   xtensa  build errors is caused by  "unable to access 
'https://github.com/espressif/esp-phy-lib.git/' "
   macOS build errors is caused by  that "accept4" and  SOCK_CLOEXEC are 
Linux-specific system calls and macro definitions.
   I have isolated them using the __APPLE__  preprocessor directive.
   


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