acassis commented on PR #19224:
URL: https://github.com/apache/nuttx/pull/19224#issuecomment-4826015716

   @speccy88 I fetched your PR and tested locally and also got an error:
   
   ```
   alan@dev:~/nuttxspace/nuttx$ git fetch upstream pull/19224/head
   alan@dev:~/nuttxspace/nuttx$ git checkout FETCH_HEAD
   alan@dev:~/nuttxspace/nuttx$ ./tools/configure.sh sim:berry
   alan@dev:~/nuttxspace/nuttx$ make
   Create version.h
   Downloading berry-4db341475df9e9ad18e6741ef978b4c467690e09.zip
     % Total    % Received % Xferd  Average Speed   Time    Time     Time  
Current
                                    Dload  Upload   Total   Spent    Left  Speed
     0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
   100  506k    0  506k    0     0   424k      0 --:--:--  0:00:01 --:--:-- 
1584k
   Unpacking berry-4db341475df9e9ad18e6741ef978b4c467690e09.zip to berry
   patching file default/berry.c
   Hunk #1 FAILED at 22 (different line endings).
   Hunk #2 FAILED at 103 (different line endings).
   Hunk #3 FAILED at 148 (different line endings).
   Hunk #4 FAILED at 151 (different line endings).
   Hunk #5 FAILED at 272 (different line endings).
   Hunk #6 FAILED at 277 (different line endings).
   Hunk #7 FAILED at 281 (different line endings).
   7 out of 7 hunks FAILED -- saving rejects to file default/berry.c.rej
   make[3]: *** [Makefile:74: berry] Error 1
   make[2]: *** [Makefile:57: 
/home/alan/nuttxspace/apps/interpreters/berry_context] Error 2
   make[1]: *** [Makefile:187: context] Error 2
   make: *** [tools/Unix.mk:471: /home/alan/nuttxspace/apps/.context] Error 2
   ```
   
   Seems like your patch 0001-Fix-Berry-default-port-for-NuttX.patch doesn't 
apply to berry-4db341475df9e9ad18e6741ef978b4c467690e09.zip
   
   Please double check, probably you used a different commit to apply it.


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