similar to: "-stdlib=libc++" applied to CMAKE_CXX_FLAGS

On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> [ brutal-snip ] >> ... >>> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more >>>

This probably just works around a layering violation. Can you provide the cmake line that produces a broken build? Cheers, Rafael On Jun 18, 2016 7:34 AM, "Nicolai Hähnle" <llvm-dev at lists.llvm.org> wrote: Hi, since recently I'm getting linker failures in debug builds. The root cause is that -fvisibility-inlines-hidden causes inline functions in explicit template

Hello, It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS into account. This is because clang_compile and clang_link_shared functions call the newly-built compiler directly, and they don't add those flags. Using CMAKE_CXX_FLAGS is necessary on systems where the C++11-enabled libstdc++ is installed not in the default location. For example, the CentOS buildbot uses:

I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. I'm trying to configure with the following options: CLANG_DEFAULT_CXX_STDLIB = libc++ CLANG_DEFAULT_RTLIB = compiler-rt

Submitted r204593. On Sun, Mar 23, 2014 at 10:03 PM, Alexey Samsonov <samsonov at google.com>wrote: > Hi Dmitri, > > On Sat, Mar 22, 2014 at 11:50 PM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > >> Hello, >> >> It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS >> into account. This is because clang_compile and

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)

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

Hey Pete, I also tried CMAKE_CXX_FLAGS_RELEASE with the same effect. On Mon, Jul 20, 2015, at 09:34 AM, Pete Cooper wrote: > Hi Adrian > > I’m not sure if the CMAKE_CXX_FLAGS is used in LLVM. We have our own > flags for different configurations. I don’t remember if our ones inherit > from CMAKE_CXX_FLAGS or override it completely. Anyway, they are: > - CMAKE_CXX_FLAGS_DEBUG

Hi Timo: You need to find LLVMConfig.cmake in the binary or install directory tree, not the source tree. Although I don't embed clang/llvm, my config might help you figure it -- clang/llvm installed under (could have used build directory) ~/usr : $ cd /Users/dhinton/projects/cover/build/ && rm -rf * && CC=~/usr/bin/clang CXX=~/usr/bin/clang++ LLVM_DIR=~/usr/lib/cmake/llvm

Am 2018-01-26 21:36, schrieb Tom Stellard via llvm-dev: > 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): >>

Hi Ivan, On Fri, Mar 28, 2014 at 3:21 PM, Ivan A. Kosarev <ivan at ivan-labs.com> wrote: > Hi Alexey, > > > On 03/27/2014 04:35 PM, Alexey Samsonov wrote: > > Here's the reason why I've made this change: > > http://llvm.1065342.n5.nabble.com/compiler-rt-CMake-build-ignores-CMAKE-CXX-FLAGS-tp67022.html > > > OK, thanks. > > BTW, should we CC

I regularly use '-DCMAKE_CXX_FLAGS' when configuring CLang/LLVM to distinguish my builds (Alpha/Beta/Final) or to build custom versions, usually by adding additional '-D' flags, but I discovered I had to add the ':STRING' qualifier to it when invoking 'cmake'. With 'gmake' this is equivalent to '--with-extra-options="whatever flags":

This is just for compiler-rt. The reason for having -fno-omit-frame-pointer is that tools like https://perf.wiki.kernel.org/index.php/Main_Page would work on ASAN binaries. Adrian On Mon, Jul 20, 2015, at 02:23 PM, adek at adek.io wrote: > Hey, > > Thanks for ideas. I tried them on, but none of them succeeded. > > If I remove this line: >

On Fri, Nov 30, 2012 at 01:41:05PM +0400, Kostya Serebryany wrote: > Just want to remind everyone that we plan to stop using mach_override in > asanin favor of OSX's native function interposition. > So, we probably don't want to spend too much effort fixing mach_override. > > --kcc Kostya, Unless I am misunderstanding the code in asan/asan_intercepted_functions.h,

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): >

+kremenek, ganna On Sat, Dec 1, 2012 at 4:33 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Fri, Nov 30, 2012 at 01:41:05PM +0400, Kostya Serebryany wrote: > > Just want to remind everyone that we plan to stop using mach_override in > > asanin favor of OSX's native function interposition. > > So, we probably don't want to spend too much effort fixing

'-DCMAKE_CXX_FLAGS=-fno-omit-frame-pointer -Wno-maybe-uninitialized -fPIC -fPIE' -- The C compiler identification is GNU 4.8.1 -- The CXX compiler identification is GNU 4.8.1 -- Check for working C compiler: /home/engshare/third-party2/gcc/4.8.1/centos6-native/cc6c9dc/bin/gcc -- Check for working C compiler: /home/engshare/third-party2/gcc/4.8.1/centos6-native/cc6c9dc/bin/gcc -- works --

> On Dec 20, 2016, at 5:49 AM, Carsten Mattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > ​Hi again, Teresa. > > Looks like I had forgotten to report back with success > when finally building 3.9.0 in ThinLTO linker mode > back in October. Sorry about that and thanks for > helping me out. I know how important it is to get > success reports as well, as a

Sorry my example wasn't helpful. I did take a quick look at rust -- though I didn't download or try to build it -- and they seem to allow you to use an installed or prebuilt version in addition to building it in-tree. However, even when they build it in-tree, they build the whole thing -- see mk/llvm.mk. Good luck... On Mon, Oct 10, 2016 at 1:33 AM, Timo Janssen via llvm-dev <

Hi all. I want to use llvm in my project and I want to make llvm a git submodule in my project. http://llvm.org/docs/CMake.html#embedding-llvm-in-your-project At this in the documentation it claims to describe how to embed llvm into a project. I tried it that way but it doesn't work, because there isn't any findLLVM.cmake in the llvm/cmake/modules directory anymore (i don't