search for: cxxabi

...$INSTALL --enable-optimized But in step 2, I have a compilation error below, -- llvm[1]: Compiling Signals.cpp for Release build In file included from /nfs_home/chenwj/test/llvm-2.9/lib/Support/Signals.cpp:30: /nfs_home/chenwj/test/llvm-2.9/lib/Support/Unix/Signals.inc:31:10: fatal error: 'cxxabi.h' file not found #include <cxxabi.h> ^ -- Do I miss something like missing option or the Clang source needed to be modified? Thanks! Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-...

...lled the binary clang package clang3.0-7. When I tried to build the latest llvm/clang from source using this binary clang I get this error: 1) In file included from /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal error: 'cxxabi.h' file not found #include <cxxabi.h> ^ llvm[1]: Compiling Statistic.cpp for Debug+Asserts build 1 error generated. gmake[1]: *** [/home/mgeldiener/dev/clang/build/lib/Support/Debug+Asserts/Signals.o] Error 1 gmake[1]: *** Waiting for unfinished jobs.... gmake[1]: Leaving directo...

...linux-gnu/4.6.3/../../../../include/c++/4.6.3/backward /usr/local/include /usr/bin/../lib/clang/3.0/include /usr/include End of search list. In file included from /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal error: 'cxxabi.h' file not found #include <cxxabi.h> ^ 1 error generated. gmake[1]: *** [/home/mgeldiener/dev/clang/build/lib/Support/Debug+Asserts/Signals.o] Error 1 gmake[1]: *** Waiting for unfinished jobs.... gmake[1]: Leaving directory `/home/mgeldiener/dev/clang/build/lib/Support' gma...

This looks relevant to me for your issue. Grabbing the cxxabi.h from there may work: http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 -- Aaron Myles Landwehr On Sat, Jul 30, 2011 at 1:33 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi, all > > I am trying to selfhost LLVM and Clang. Below is my flow, > > Step 1. Bui...

Hi, Asron > This looks relevant to me for your issue. Grabbing the cxxabi.h from there > may work: > > http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 I am not sure where to put cxxabi.h. How can I let clang find this header file while compiling LLVM and Clang (in step 2)? Thanks! Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems L...

...g3.0-7. When I > tried to build the latest llvm/clang from source using this binary clang > I get this error: > > 1) In file included from > /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: > /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal > error: 'cxxabi.h' file not found > #include <cxxabi.h> > ^ > llvm[1]: Compiling Statistic.cpp for Debug+Asserts build > 1 error generated. > gmake[1]: *** > [/home/mgeldiener/dev/clang/build/lib/Support/Debug+Asserts/Signals.o] > Error 1 > gmake[1]: *** Waiting for unfin...

...to use the in-tree libcxx but looks for one built >> and installed in the system. > > > IIRC, -DLLVM_ENABLE_LIBCXX reduces to passing --stdlib=libc++ (see > [1]) to the compiler. > > What you can do is a two-stage build. On the first stage, build just > libc++ (ninja cxx cxxabi). On the second stage, re-configure with > -DLLVM_ENABLE_LIBCXX and build the rest of the tools. We have a > downstream builder that works this way to avoid a libstdc++ defect > on the host platform. I can't remember the exact details, can dig > them up if it helps. Yes please, tha...

...g3.0-7. When I > tried to build the latest llvm/clang from source using this binary clang > I get this error: > > 1) In file included from > /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: > /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal > error: 'cxxabi.h' file not found > #include <cxxabi.h> > ^ > llvm[1]: Compiling Statistic.cpp for Debug+Asserts build > 1 error generated. > gmake[1]: *** > [/home/mgeldiener/dev/clang/build/lib/Support/Debug+Asserts/Signals.o] > Error 1 > gmake[1]: *** Waiting for unfin...

...d to build the latest llvm/clang from source using this binary clang >> I get this error: >> >> 1) In file included from >> /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: >> /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal >> error: 'cxxabi.h' file not found >> #include <cxxabi.h> >> ^ >> llvm[1]: Compiling Statistic.cpp for Debug+Asserts build >> 1 error generated. >> gmake[1]: *** >> [/home/mgeldiener/dev/clang/build/lib/Support/Debug+Asserts/Signals.o] >> Error 1 >>...

...tired of LLVM's PrintStackTrace() function only being able to print mangled C++ names. I went ahead and wrote a demangler (shown below), however there's one slight problem, which is that the output of backtrace_symbols appears to be different on different platforms. In order to use the cxxabi demangler, you need to provide it with the portion of each line that contains the mangled name, and strip all of the other items on that line. In the case of OS X, the mangled symbol is delimited by whitespace, however on some platforms it appears that the mangled name is surrounded by parenthe...

On Sat, Jul 30, 2011 at 2:35 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi, Asron > > > This looks relevant to me for your issue. Grabbing the cxxabi.h from > there > > may work: > > > > http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 > > I am not sure where to put cxxabi.h. How can I let clang find this > header file while compiling LLVM and Clang (in step 2)? > You need to add it to somewhere...

If you're willing to install libc++ you can easily work around this by running `ninja install-cxx install-cxxabi` before running any of the LLVM or Clang build targets. /Eric On Tue, Dec 27, 2016 at 7:45 AM, Carsten Mattner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake > <asiri.rathnayake at gmail.com> wrote: > > > > >...

...seeing in the LLVM bitcode. > > As an FYI, on Unix, the c++filt program will demangle names (although > sometimes you have to remove an extra '_' from the front of the name to get > it to work). there's also a __cxa_demangle function in http://llvm.org/svn/llvm-project/libcxxabi/trunk/include/cxxabi.h

...hat > it doesn't try to use the in-tree libcxx but looks for one built and > installed > in the system. > IIRC, -DLLVM_ENABLE_LIBCXX reduces to passing --stdlib=libc++ (see [1]) to the compiler. What you can do is a two-stage build. On the first stage, build just libc++ (ninja cxx cxxabi). On the second stage, re-configure with -DLLVM_ENABLE_LIBCXX and build the rest of the tools. We have a downstream builder that works this way to avoid a libstdc++ defect on the host platform. I can't remember the exact details, can dig them up if it helps. Cheers, / Asiri [1] http://libcxx...

If you want to get the original name by a library function, as Jonathan mentioned, you can call __cxa_demangle in cxxabi.h. However, this API is only available in gcc. If you want something more portable, try glog or libibert, notice libibert is GPL licensed. On Thu, Dec 11, 2014 at 7:57 AM, Roel Jordans <r.jordans at tue.nl> wrote: > When a C++ compiler translates source code it will perform name mangling...

...ect value of "cxxrt" on FreeBSD. I am going to try the following diff: >> >> --- llvm.src/projects/libcxx/CMakeLists.txt >> +++ llvm.src/projects/libcxx/CMakeLists.txt >> @@ -135,6 +135,8 @@ >> elseif (APPLE) >> set(LIBCXX_CXX_ABI_LIBNAME "libcxxabi") >> set(LIBCXX_CXX_ABI_SYSTEM 1) >> + elseif (CMAKE_SYSTEM_NAME MATCHES "FreeBSD") >> + set(LIBCXX_CXX_ABI_LIBNAME "libcxxrt") >> else() >> set(LIBCXX_CXX_ABI_LIBNAME "default") >> endif() > > ... and unfortu...

...one built > >> and installed in the system. > > > > > > IIRC, -DLLVM_ENABLE_LIBCXX reduces to passing --stdlib=libc++ (see > > [1]) to the compiler. > > > > What you can do is a two-stage build. On the first stage, build just > > libc++ (ninja cxx cxxabi). On the second stage, re-configure with > > -DLLVM_ENABLE_LIBCXX and build the rest of the tools. We have a > > downstream builder that works this way to avoid a libstdc++ defect > > on the host platform. I can't remember the exact details, can dig > > them up if it hel...

What is the purpose of supporting this "copy directories around" sort of build strategy anyway? At the end of the day, the way these packages get installed is via system package managers is independently, each project finding its dependencies with the standard prefix path. When I compile from source it's always like this: $ cd llvm-6.0.0rc2.src/ $ mkdir build $ cd build $ cmake ..

...wn what the set of supported use cases for building the runtime libraries are. In particular, the world I would like to live in is one where the only way to build libc++/libc++abi/libunwind is: $ mkdir build $ cd build $ cmake <monorepo-root>/llvm -DLLVM_ENABLE_PROJECTS=libcxx;libcxxabi;libunwind <options> $ ninja -C build install-{cxx,cxxabi,unwind} The "runtimes" build would be built on top of this -- it would be just a driver for building these libraries using documented options against the just-built Clang. I think it already does so in essence, however if...

...being set to the correct value of "cxxrt" on FreeBSD. I am going to try the following diff: > > --- llvm.src/projects/libcxx/CMakeLists.txt > +++ llvm.src/projects/libcxx/CMakeLists.txt > @@ -135,6 +135,8 @@ > elseif (APPLE) > set(LIBCXX_CXX_ABI_LIBNAME "libcxxabi") > set(LIBCXX_CXX_ABI_SYSTEM 1) > + elseif (CMAKE_SYSTEM_NAME MATCHES "FreeBSD") > + set(LIBCXX_CXX_ABI_LIBNAME "libcxxrt") > else() > set(LIBCXX_CXX_ABI_LIBNAME "default") > endif() ... and unfortunately that didn't work, s...