similar to: [LLVMdev] bugs in CMake build

[I'm cc-ing the mailing list because there are some topics here of general interest] HyperQuantum <hyperquantum at gmail.com> writes: >> CMAKE_SOURCE_DIR should be the same as LLVM_MAIN_SRC_DIR. If you know an >> scenario where this is not true, please describe it. > > In my case it's not true. I have put LLVM in a subdirectory of my > project

Hans, I have posted a complete patch for solving the linkage issues with LLVM_LINK_LLVM_DYLIB on Phabricator at http://reviews.llvm.org/D16945. The bulk of the fix the simple changes of... Index: cmake/modules/AddLLVM.cmake =================================================================== --- cmake/modules/AddLLVM.cmake (revision 259743) +++ cmake/modules/AddLLVM.cmake (working copy) @@

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

Hello, I work on CMake upstream. I'd like to find out in what ways CMake upstream does not fit the needs of llvm/clang, and then fill those gaps. The recent update of the minimum version to CMake 2.8.8 is a good start. Before being able to assess what is missing, it should be ensured that the current codebase is as modern as the minimum version allows, and it needs to be cleaned up. 1)

Currently, cmake policies are manually maintained by each project. This is done via a set of `cmake_policy()` commands following the initial `cmake_minimum_required()` command at the top of each CMakeLists.txt project file. Somewhat surprisingly, these sets are local to each project and independent of each other -- even for in-tree builds containing multiple sub-projects. This is because cmake

On Thu, Feb 28, 2008 at 7:26 PM, Mike Stump <mrs at apple.com> wrote: > On Feb 28, 2008, at 4:03 AM, HyperQuantum wrote: > > llvm-gcc: error trying to exec 'cc1': execvp: No such file or > > directory > > Do: > > find . -name cc1 -print > > to find cc1 in the build directory. Then, copy this file by hand to > to llvm-gcc

On Fri, Feb 29, 2008 at 2:23 PM, HyperQuantum <hyperquantum at gmail.com> wrote: > At least I got llvm-gcc running again. Something is still wrong because I cannot get Pi_Calc to run after compiling it with this semi-cross-compiler, and it worked with the regular llvm-gcc. I configured the cross compiler with target mips-unknown-linux-gnu. Should I use another triple or do I need to

How can I allocate an array with a size that is not known at compile time? The language reference says that the array size must be a constant integer value. It also says that variable sized arrays are represented by using zero as the number of elements. Obviously I cannot use zero in the array type when it is allocated. llvm-gcc seems to use a pointer type instead of an array type, so compiling a

Alright, this version works for me. Anything else that needs to be done? -Alex > On Oct 7, 2015, at 8:15 PM, Alex Wang <aw1621107 at gmail.com> wrote: > > diff --git a/cmake/modules/TableGen.cmake b/cmake/modules/TableGen.cmake > index 452a728..cb06450 100644 > --- a/cmake/modules/TableGen.cmake > +++ b/cmake/modules/TableGen.cmake > @@ -70,6 +70,15 @@

Hi all, CMake seems to have broken in the last few days - or is it just me? tcare:llvm-release tcare$ make -j4 -- Target triple: x86_64-apple-darwin10.5.0 -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Targeting X86 CMake Error at cmake/modules/LLVMConfig.cmake:90 (message): Library LLVMARMAsmParser not found in list of llvm libraries. Call Stack (most

It should probably be inside an `if(LLVM_USE_HOST_TOOLS)` block. That way the extra target and command won’t get added unless needed and CMake won’t spew dev warnings. Adding a target with a nonexistent dependency makes CMake dump a bunch of developer warnings. Other than that this looks good. Does it resolve the issue for you? -Chris > On Oct 7, 2015, at 4:09 PM, Alex Wang <aw1621107 at

Looks good to me! I can commit this for you today. Thanks! -Chris > On Oct 19, 2015, at 2:40 PM, Alex Wang via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Looks like the LLVMSupport patch didn't get everything -- build failed in the > same way on libLLVMTableGen. Problem/solution looked the same as for > LLVMSupport, so just tweaked the previous patch, and

On Sat, Nov 1, 2008 at 12:50 AM, Chris Lattner <clattner at apple.com> wrote: > > On Oct 31, 2008, at 2:04 PM, Óscar Fuentes wrote: >> There is no reason to include the CMake build system on this >> release. It >> is undocumented and immature. >> >> Please remove the cmake/ directory and all files named CMakeLists.txt >> from the LLVM source tree.

>> +//===-- Regex.h - Regular Expression matcher implementation -------------===// > > Include C++ marker please (*- C++ -*-===//) Just out of curiosity, what is this marker used for?

Hi Philip, thanks for the quick answer. That makes sense, but when leaving the set LLVM_LINK_COMPONENTS out I get an undefined symbol when loading the plugin: _ZTVN4llvm2cl3optINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEELb0ENS0_6parserIS7_EEEE which boils down to llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char>>,

I'm seeing this as well, but for the LLVMAlphaAsmParser: CMake Error at cmake/modules/LLVMConfig.cmake:90 (message): Library LLVMAlphaAsmPrinter not found in list of llvm libraries. Call Stack (most recent call first): cmake/modules/LLVMConfig.cmake:27 (explicit_map_components_to_libraries) cmake/modules/LLVMConfig.cmake:20 (explicit_llvm_config) cmake/modules/AddLLVM.cmake:61

When I compile the latest CVS, I get the following error: Compiling param/params.c gcc.colorgcc: Internal compiler error: program cpp got fatal signal 11 make: *** [param/params.o] Error 1 What did I do wrong?? Stephen Gerstacker The Gradall Company phone: 339-2211 ext. 8814 ******************************************************* The information contained in this transmission is

On 5/14/2012 10:28 AM, Jim Grosbach wrote: > > On May 14, 2012, at 10:21 AM, Ashok Nalkund<ashoknn at qualcomm.com> wrote: > >> On 5/14/2012 9:51 AM, Jim Grosbach wrote: >>> >>>>> >>>>> If you're hitting that code, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT. >>>>>

On Wed, Jul 16, 2008 at 11:07 AM, HyperQuantum <hyperquantum at gmail.com> wrote: > How can I allocate an array with a size that is not known at compile time? > > The language reference says that the array size must be a constant > integer value. It also says that variable sized arrays are represented > by using zero as the number of elements. Obviously I cannot use zero >

Hi, I'm working on an LLVM Pass plugin and I'm running into a problem when loading it into opt. I want to have a custom option for my pass and added an llvm::cl::opt #include'ing "llvm/Support/CommandLine.h" linking the dependant libs causes the following error when loading it with opt: opt: CommandLine Error: Option 'debug-pass' registered more than once! I