simbit18 commented on PR #17968:
URL: https://github.com/apache/nuttx/pull/17968#issuecomment-3761212770

   Hi @trns1997, I ran a test with our docker image using your 
“add-missing-libcxxtoolchain-support” branch  
     with the cmake build for xmc4800-relax:nsh and it is still broken.
   
   ```
   [1119/1124] Building CXX object 
apps/testing/cxx/cxxtest/CMakeFiles/apps_cxxtest.dir/cxxtest_main.cxx.obj
   FAILED: 
apps/testing/cxx/cxxtest/CMakeFiles/apps_cxxtest.dir/cxxtest_main.cxx.obj 
   /tools/ccache/bin/arm-none-eabi-g++ -D__NuttX__ -Dmain=cxxtest_main 
-I/github/workspace/sources/apps/include 
-I/github/workspace/sources/nuttx/build/apps/include -isystem 
/github/workspace/sources/nuttx/include -isystem 
/github/workspace/sources/nuttx/build/include -mtune=cortex-m4 -march=armv7e-m 
-mfpu=fpv4-sp-d16 -mfloat-abi=hard --param=min-pagesize=0 -fno-common -Wall 
-Wshadow -Wundef -nostdlib -fomit-frame-pointer -mthumb -Wa,-mthumb 
-Wa,-mimplicit-it=always -ffunction-sections -fdata-sections -Wno-attributes 
-Wno-unknown-pragmas -Wno-psabi -std=c++17 -fdiagnostics-color=always -DNDEBUG 
-fmacro-prefix-map=/github/workspace/sources/nuttx= 
-fmacro-prefix-map=/github/workspace/sources/apps= 
-fmacro-prefix-map=/github/workspace/sources/nuttx/boards/arm/xmc4/xmc4800-relax=
 -fmacro-prefix-map=/github/workspace/sources/nuttx/arch/arm/src/xmc4= 
@apps/testing/cxx/cxxtest/CMakeFiles/apps_cxxtest.dir/cxxtest_main.cxx.obj.rsp 
-MD -MT apps/testing/cxx/cxxtest/CMakeFiles/apps_cxxtest.dir/c
 xxtest_main.cxx.obj -MF 
apps/testing/cxx/cxxtest/CMakeFiles/apps_cxxtest.dir/cxxtest_main.cxx.obj.d -o 
apps/testing/cxx/cxxtest/CMakeFiles/apps_cxxtest.dir/cxxtest_main.cxx.obj -c 
/github/workspace/sources/apps/testing/cxx/cxxtest/cxxtest_main.cxx
   In file included from 
/tools/gcc-arm-none-eabi/arm-none-eabi/include/c++/13.2.1/cstdlib:79,
                    from 
/tools/gcc-arm-none-eabi/arm-none-eabi/include/c++/13.2.1/ext/string_conversions.h:43,
                    from 
/tools/gcc-arm-none-eabi/arm-none-eabi/include/c++/13.2.1/bits/basic_string.h:4097,
                    from 
/tools/gcc-arm-none-eabi/arm-none-eabi/include/c++/13.2.1/string:54,
                    from 
/github/workspace/sources/apps/testing/cxx/cxxtest/cxxtest_main.cxx:38:
   Error: /tools/gcc-arm-none-eabi/arm-none-eabi/include/stdlib.h:39:3: error: 
conflicting declaration 'typedef struct div_t div_t'
      39 | } div_t;
         |   ^~~~~
   In file included from 
/github/workspace/sources/nuttx/include/nuttx/kmalloc.h:34,
                    from 
/github/workspace/sources/nuttx/include/nuttx/lib/lib.h:32,
                    from /github/workspace/sources/nuttx/include/stdio.h:37,
                    from 
/tools/gcc-arm-none-eabi/arm-none-eabi/include/c++/13.2.1/cstdio:42,
                    from 
/github/workspace/sources/apps/testing/cxx/cxxtest/cxxtest_main.cxx:29:
   /github/workspace/sources/nuttx/include/stdlib.h:98:22: note: previous 
declaration as 'typedef struct div_s div_t'
      98 | typedef struct div_s div_t;
         |                      ^~~~~
   Error: /tools/gcc-arm-none-eabi/arm-none-eabi/include/stdlib.h:45:3: error: 
conflicting declaration 'typedef struct ldiv_t ldiv_t'
      45 | } ldiv_t;
         |   ^~~~~~
   /github/workspace/sources/nuttx/include/stdlib.h:108:23: note: previous 
declaration as 'typedef struct ldiv_s ldiv_t'
     108 | typedef struct ldiv_s ldiv_t;
         |                       ^~~~~~
   Error: /tools/gcc-arm-none-eabi/arm-none-eabi/include/stdlib.h:52:3: error: 
conflicting declaration 'typedef struct lldiv_t lldiv_t'
      52 | } lldiv_t;
         |   ^~~~~~~
   /github/workspace/sources/nuttx/include/stdlib.h:118:24: note: previous 
declaration as 'typedef struct lldiv_s lldiv_t'
     118 | typedef struct lldiv_s lldiv_t;
         |                        ^~~~~~~
   ninja: build stopped: subcommand failed.
   ```


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