similar to: [LLVMdev] [cfe-dev] Cannot run clang regression tests with cmake

If your cut-n-paste is accurate, you seem to be missing a closing quote for CMAKE_CXX_LINK_FLAGS. hth... don On Jul 8, 2015 2:22 AM, "David A. Greene" <greened at obbligato.org> wrote: > greened at obbligato.org (David A. Greene) writes: > > > I looked at the instructions on the libc++ page and for Linux it > > recommends building with -stdlib=libc++ -lc++abi.

Hi Eli and Others In response to your feedback, I have taken care of all your review comments - I removed clangOMP.a and moved the implementation of "class OmpPragmaHandler" to "clangLex.a". The attached zipped file - namely - 'OpenMP_support_in_Clang.tar.gz' contains all the implemented "patches" along with *newly* added source files. Another attached text

Hi Steve, On Thu, 15 Jan 2009, steve naroff wrote: > For development, CMake is working great for me. I rarely get build > errors related to the project file being out-of-date. > > Is it true that CMake only generates absolute paths? Any idea on the > difficulty of generating relative paths? I consider this a pretty big > obstacle... I did not follow the full-thread, just

On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/19/2020 09:05 PM, Sedat Dilek wrote: > > Hi Tom, > > > > thanks and congrats for LLVM 10.0.1-rc1 release. > > > > [1] shows 2 assets. > > 10.0.0 RCs had a lot of more assets. > > I am missing the llvm-project-10.0.1rc1.tar.xz tarball. > > > > Will

On Wed, May 20, 2020 at 11:12 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/20/2020 09:53 AM, Sedat Dilek wrote: > > On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > >> > >> On 05/19/2020 09:05 PM, Sedat Dilek wrote: > >>> Hi Tom, > >>> > >>> thanks and congrats for LLVM

Hello. When i run llvm-config --libs jit bitreader bitwriter ipo linker engine i get: -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMMCParser -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMX86Info -lLLVMLinker -lLLVMArchive -lLLVMipo -lLLVMBitWriter -lLLVMBitReader -lLLVMJIT -lLLVMExecutionEngine -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > >>>> Isn't is possible for cmake just to glob everything in the corresponding >>>> directory? >>>> >>>> >>> Yes, but then the build would not notice a change on the file >>> structure. You'll need to explicitly invoke

Kenneth Boyd <zaimoni at zaimoni.com> writes: >>> Isn't is possible for cmake just to glob everything in the corresponding >>> directory? >>> >> >> Yes, but then the build would not notice a change on the file >> structure. You'll need to explicitly invoke cmake for being sure that >> whatever changes were made by the last svn

[cc-ing llvm-dev] arrowdodger <6yearold at gmail.com> writes: > Hello. I've found that CMake-generated llvm-config contains -pedantic flag, > if LLVM_ENABLE_PEDANTIC was ON during cmake configuration. > This forces all llvm-config clients to build their sources with -pedantic, > which, i think, is kind of wrong. > For example, it's not possible to build LDC (LLVM D

Óscar Fuentes wrote: > "Anton Korobeynikov" <asl at math.spbu.ru> writes: > > >>> at all, it would be great if you reflect your changes on the file list >>> inside the corresponding CMakeLists.txt when you add, remove or rename >>> a .cpp file. >>> >> Isn't is possible for cmake just to glob everything in the

"Anton Korobeynikov" <asl at math.spbu.ru> writes: >> at all, it would be great if you reflect your changes on the file list >> inside the corresponding CMakeLists.txt when you add, remove or rename >> a .cpp file. > > Isn't is possible for cmake just to glob everything in the corresponding > directory? Yes, but then the build would not notice a

Hi, Oscar > at all, it would be great if you reflect your changes on the file list > inside the corresponding CMakeLists.txt when you add, remove or rename a > .cpp file. Isn't is possible for cmake just to glob everything in the corresponding directory? -- WBR, Anton Korobeynikov

On Oct 26, 2008, at 11:17 AM, Óscar Fuentes wrote: >> It would be simpler for autoconf builds to have a Perl script that >> updates the CMakeLists.txt files when necessary. (This doesn't look >> *that* hard, but I can't say when I'll surface long enough to work >> on that.) > > In theory, it is possible to do this with cmake itself. In practice, >

Hi, when I run cmake I get the following warning: --------------------------------------------------------------------------------------- CMake Warning at cmake/modules/HandleLLVMStdlib.cmake:24 (message): Can't specify libc++ with '-stdlib=' Call Stack (most recent call first): cmake/config-ix.cmake:15 (include) CMakeLists.txt:580 (include)

Patrick Boettcher <pb at linuxtv.org> writes: >> For development, CMake is working great for me. I rarely get build >> errors related to the project file being out-of-date. >> >> Is it true that CMake only generates absolute paths? Any idea on the >> difficulty of generating relative paths? I consider this a pretty big >> obstacle... > > I did not

Dear all, I am trying to build the llvm with cmake and using the following checkouts. LLVM version 3.2svn clang version 3.2 (trunk 158320) (llvm/trunk 158308) cmake runs with default configuration without any problem. cmake ../llvm -- Target triple: i686-pc-linux-gnu -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Constructing LLVMBuild project information --

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

On 01/26/2018 12:32 PM, Simone Atzeni via llvm-dev wrote: > Hi, > > when I run cmake I get the following warning: > > --------------------------------------------------------------------------------------- > CMake Warning at cmake/modules/HandleLLVMStdlib.cmake:24 (message): > Can't specify libc++ with '-stdlib=' > Call Stack (most recent call first): >

Fixes build of bugpoint, llvm-ld and opt. OK for commit? --- CMakeLists.txt | 1 + tools/bugpoint/CMakeLists.txt | 2 +- tools/llvm-ld/CMakeLists.txt | 2 +- tools/opt/CMakeLists.txt | 2 +- 4 files changed, 4 insertions(+), 3 deletions(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index 9bce039..0edd509 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@

On Thu, Dec 19, 2013 at 8:15 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > > the other thing we need to determine is > > > > whether or not we want to maintain a stable ABI for the bugfix > > > > releases. > > > > With 3.3, the plan was to have a stable ABI, but this caused me > > > > to reject several fixes. I would recommend