Xiang you are amazing! It built flawlessly and the bundled example hellocxx is up and running. Thank you so much!
Also, a big thank you NuttX developers for your hard work on this project! Matt On Sun, Aug 16, 2020 at 8:30 AM Xiang Xiao <xiaoxiang781...@gmail.com> wrote: > I just append a new patch to PR 1592, please try it: > > https://github.com/apache/incubator-nuttx/pull/1592/commits/79afeea64be227e218176805970cca1b2287ba29 > > > > -----Original Message----- > > From: Matt DeWall <mdew...@gmail.com> > > Sent: Sunday, August 16, 2020 2:28 AM > > To: dev@nuttx.apache.org > > Subject: Re: cpp cxx help - No thread API > > > > Thanks Xiang - that got me to the linking step! I'm getting this error: > > > > make[2]: Leaving directory > > '/nuttx/nuttx_patch/nuttx/boards/arm/stm32/common' > > LD: nuttx > > arm-none-eabi-ld: > > > /tools/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/lib/thumb/v7- > > m/nofp//libsupc++.a(vterminate.o): > > in function `__gnu_cxx::__verbose_terminate_handler()': > > vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xf4): > > undefined reference to `_impure_ptr' > > make[1]: *** [Makefile:172: nuttx] Error 1 > > make[1]: Leaving directory '/nuttx/nuttx_patch/nuttx/arch/arm/src' > > make: *** [tools/Makefile.unix:401: nuttx] Error 2 > > > > I tried the hack going around about using this to overwrite > vterminate.cc for the uclib library: > > > > arm-none-eabi-ar -x libsupc++.a vterminate.o > > > > I was able to generate vterminate.o in that way but the "hack" mentions > overwriting an existing vterminate.o. I can't find > > vterminate.o anywhere else in the project. > > > > Probably doesn't matter, but here's the part of a map generated with > LDFLAGS where it references the _impure_ptr > > > > ... > > _exit > > /nuttx/nuttx_patch/nuttx/staging/libsched.a(exit.o) > > > > /nuttx/nuttx_patch/nuttx/staging/libsched.a(pthread_exit.o) > > _impure_ptr > > > /tools/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/lib/thumb/v7- > > m/nofp//libsupc++.a(vterminate.o) > > _sbss > > /nuttx/nuttx_patch/nuttx/staging/libarch.a(stm32_start.o) > > ... > > > > > > > > > > On Fri, Aug 14, 2020 at 8:24 PM Xiang Xiao <xiaoxiang781...@gmail.com> > > wrote: > > > > > Only PMC/committer have the permission to update those repositories if > > > I remember correctly, so we can manage github.com/nuttx using the same > > > Apache process. > > > > > > > -----Original Message----- > > > > From: Gregory Nutt <spudan...@gmail.com> > > > > Sent: Saturday, August 15, 2020 3:27 AM > > > > To: dev@nuttx.apache.org > > > > Subject: Re: cpp cxx help - No thread API > > > > > > > > > > > > > Guys, I think we should move your bitbucket libcxx to > > > > > github.com/nuttx to make it more official. > > > > > > > > > > What do you think? Other (better) option should including official > > > > > support to NuttX on llvm libcxx. > > > > > > > > i would NEVER recommend github.com/nuttx for any significant use. > > > There are many people with totally uncontrolled write access > > > > those repositories. There are not controls, no reviews, no > > > > management, > > > no checks and balances. It is complete unsafe to store > > > > anything that people really depend on. > > > > > > > > I have suggested in the past that we bring those directories under > > > > the > > > project management umbrella, but for no those are unsafe, > > > > unmanaged, garbage repositories. DO NOT PUT ANTYTHING YOU CARE > > > > ABOUT > > > THERE. > > > > > > > > That can change. but that is the current state: Unsafe and only > > > > suited > > > for garbage. > > > > > > > > > > >
