search for: llvm_requires_rtti

...or building LLVM but appending > to your `make' command the text "VERBOSE=1" and then show the compiler > command line for one .cpp file (lib/MC/MCAsmInfo.cpp is the best > candidate.) > There is (was?) a CMake variable for this if you're going that route. Setting LLVM_REQUIRES_RTTI=1 enabled an RTTI build that I haven't had issues with. I don't know what the ./configure equivalent is, sorry. -Gordon > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.c...

Gordon Keiser <gkeiser at arxan.com> writes: > There is (was?) a CMake variable for this if you're going that route. > Setting LLVM_REQUIRES_RTTI=1 enabled an RTTI build that I haven't had > issues with. I don't know what the ./configure equivalent is, sorry. LLVM_REQUIRES_RTTI is an internal variable. It works as you say, but there is no guarantee about it. Adding a proper option for enabling RTTI on the CMake build is trivial,...

...e associated error message(s). RTTI is an on/off option that changes per LLVM library, so setting -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti while most of the rest have -fno-rtti. The switch is decided on cmake/modules/LLVMProcessSources.cmake depending on the value of LLVM_REQUIRES_RTTI. [snip]

...> > RTTI is an on/off option that changes per LLVM library, so setting > -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti > while most of the rest have -fno-rtti. The switch is decided on > cmake/modules/LLVMProcessSources.cmake depending on the value of > LLVM_REQUIRES_RTTI. > > > Hello! I'm sorry, because I've already solved the build problem with the mentioned app manually, now it's not very convenient for me to reproduce the error for the moment. I agree that "RTTI is an on/off option". But I think the point of the problem I mentioned...

Hello LLVM-DEV! Recently I think I found a bug in llvm's CMakeLists.(I use llvm 3.1svn and Clang 3.1) I follow the normal way to try to compile an application that utilize both clang and llvm: I ./autogen.sh it, ./configure it and make it. But the make fails. At last I found out the failure is because that the Makefile's CXXFLAGS does not contain -fno-rtti option which is needed by the

...is an on/off option that changes per LLVM library, so setting >> -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti >> while most of the rest have -fno-rtti. The switch is decided on >> cmake/modules/LLVMProcessSources.cmake depending on the value of >> LLVM_REQUIRES_RTTI. >> >> >> Hello! I'm sorry, because I've already solved the build problem with the > mentioned app manually, now it's not very convenient for me to reproduce > the error for the moment. I agree that "RTTI is an on/off option". But I > think the point...

On Thu, Oct 14, 2010 at 4:09 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Francois, > >> In that case, RTTI and exception should also be disabled from CMake >> generated projects right? >> Currently they are enabled all over my MSVC projects. > > I'm not sure what you are asking.  The goal is for LLVM to not require > RTTI or exception handling.

Vladimir Pouzanov <farcaller at gmail.com> writes: > On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: >> Llvm typically doesn't build with RTTI enabled. Perhaps that's what >> you're running into? >> > I've actually tried to compile both LLVM and my lib with -frtti with > same results. Please show the exact commands

I've actually tried to compile both LLVM and my lib with -frtti with same results. On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: > Llvm typically doesn't build with RTTI enabled. Perhaps that's what you're running into? > > Jim -- Vladimir Pouzanov http://www.farcaller.net/ -------------- next part -------------- A non-text attachment

On Mon, Feb 8, 2016 at 12:45 PM, Hans Wennborg <hans at chromium.org> wrote: > Chris Bieneman is probably your best bet, and maybe also Dan Liew. > Hans, My current, and hopefully final, revision of the proposed patch is simplified and reworked to solve the problem entirely from cmake without touching the the llvm-build python scripts. Basically, the new fix for avoiding the

Ah! Think I figured it out -- it's rtti. When I build with -fno-rtti, the spurious symbol disappears. Blargh, that was complicated. I'm going to try an out-of-source cmake build now. So far this has been a soliloquy, hope it helps someone else. ________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Charles Jacobsen

...that changes per LLVM library, so setting > >> -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti > >> while most of the rest have -fno-rtti. The switch is decided on > >> cmake/modules/LLVMProcessSources.cmake depending on the value of > >> LLVM_REQUIRES_RTTI. > >> > >> > >> Hello! I'm sorry, because I've already solved the build problem with the > > mentioned app manually, now it's not very convenient for me to reproduce > > the error for the moment. I agree that "RTTI is an on/off option". B...

Hi all, I am having some some trouble with LLVM 3.8... I built it with GCC 4.8.2 with cmake and no special CXX/C flags. That means in case of GCC that RTTI is switched on, I believe. However, building my MCJIT application against the just built LLVM and linking results in: libqdp.a(qdp_llvm.o):(.rodata._ZTIN4llvm8FCmpInstE[_ZTIN4llvm8FCmpInstE]+0x10): undefined reference to `typeinfo for