snikeguo commented on issue #18232:
URL: https://github.com/apache/nuttx/issues/18232#issuecomment-3861302869

   > Hi [@snikeguo](https://github.com/snikeguo), this PR 
[#18308](https://github.com/apache/nuttx/pull/18308) has been merged. Does that 
solve your issue ?
   
   no,demo code:
   
   ```
   
   #include <stdint.h>
   #include <stddef.h>
   #include <stdio.h>
   #include <stdlib.h>
   #include <string.h>
   #include <wchar.h>
   #include <assert.h>
   #include <stdarg.h>
   #include <memory.h>
   #include <limits.h>
   #include <math.h>
   
   #include <new>
   #include <type_traits>
   #include <limits>
   #include <algorithm>
   #include <pthread.h>
   using namespace std;
   
   int foo(){}
   
   ```
   
   common config:
   ```
   CONFIG_HAVE_CXX=y
   CONFIG_HAVE_CXXINITIALIZE=y
   CONFIG_LIBCXXTOOLCHAIN=y
   CONFIG_LIBSUPCXX_TOOLCHAIN=y
   ```
   
   .config:
   ```
   CONFIG_LIBM=y  # use nuttx math lib
   ```
   build ok .
   
   .config:
   ```
   CONFIG_LIBM_TOOLCHAIN=y # use tool chain libm
   ```
   build failed:
   ```
   In file included from 
D:/Project/runtime_nuttx/src/nuttx_workspace/apps/ics/NativeAot/user_code/usercode.cpp:220:
   
D:/Soft/ArmGcc/xpack-arm-none-eabi-gcc-13.3.1-1.1/arm-none-eabi/include/c++/13.3.1/math.h:38:12:
 error: 'abs' has not been declared in 'std'
      38 | using std::abs;
         |            ^~~
   
D:/Soft/ArmGcc/xpack-arm-none-eabi-gcc-13.3.1-1.1/arm-none-eabi/include/c++/13.3.1/math.h:39:12:
 error: 'acos' has not been declared in 'std'
      39 | using std::acos;
         |            ^~~~
   
D:/Soft/ArmGcc/xpack-arm-none-eabi-gcc-13.3.1-1.1/arm-none-eabi/include/c++/13.3.1/math.h:40:12:
 error: 'asin' has not been declared in 'std'
      40 | using std::asin;
   ```
   


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