search for: dcmake_buil

...alloc() must be > "statically" intercepted before __asan_init is called from the CRT > (hence before "dynamic" interceptors are set up). > > Can you please compare what happens in your build configuration compared to: > $ cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release > -DLLVM_TARGETS_TO_BUILD=X86 .. && ninja > instead? Do I need something special to support ninja? E:\llvm\compiler-rt-ninja>cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUIL D_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 ..\compiler-rt && ninja CMake Error...

...cally" intercepted before __asan_init is called from the CRT >>> (hence before "dynamic" interceptors are set up). >>> >>> Can you please compare what happens in your build configuration compared to: >>> $ cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release >>> -DLLVM_TARGETS_TO_BUILD=X86 .. && ninja >>> instead? >> >> Do I need something special to support ninja? > > Put it onto your PATH? > e.g. you can > $ svn export http://src.chromium.org/svn/trunk/tools/depot_tools/ninja.exe > an...

I think this issue is that we were not using the INTERCEPTOR macros to define these functions. The following patch seems to work for me to get the build linking again, however, I cannot test -- when I run check-asan, I get: 2> lit.py: lit.common.cfg:59: fatal: Invalid llvm_tools_dir config attribute: 'E:/llvm/2013/$(Configuration)/bin' ~Aaron On Thu, Oct 23, 2014 at 1:20 PM, Aaron