[llvm-dev] asan link failure when configuring with -DBUILD_SHARED_LIBS=ON

Alexey Samsonov via llvm-dev llvm-dev at lists.llvm.org
Fri Feb 26 11:35:37 PST 2016


Looking

On Thu, Feb 25, 2016 at 9:13 PM, Kostya Serebryany <kcc at google.com> wrote:

> +Alexey
>
> On Thu, Feb 25, 2016 at 5:30 AM, Diego Novillo <dnovillo at google.com>
> wrote:
>
>>
>> I'm getting this link failure when running ninja check on Linux.  I'm
>> configuring with shared libraries enabled, so I'm not sure why asan is
>> looking for .a archives.
>>
>> $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DLLVM_BUILD_TESTS=ON
>> -DCLANG_INCLUDE_DOCS=ON -DBUILD_SHARED_LIBS=ON ../llvm
>> $ ninja check-all
>> FAILED: cd [..]bld/projects/compiler-rt/lib/asan/tests &&
>> [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_globals_test.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_interface_test.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_test.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_oob_test.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_mem_test.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_str_test.cc.i386-with-calls.o
>> ASAN_INST_TEST_OBJECTS.asan_test_main.cc.i386-with-calls.o -o
>> [...]/bld/projects/compiler-rt/lib/asan/tests/default/Asan-i386-with-calls-Test
>> -Wl,-allow-shlib-undefined --driver-mode=g++ -fsanitize=address -m32
>> /usr/bin/ld: cannot find
>> [...]/bld/bin/../lib/clang/3.9.0/lib/linux/libclang_rt.asan-i386.a: No such
>> file or directory
>> /usr/bin/ld: cannot find
>> [...]/bld/bin/../lib/clang/3.9.0/lib/linux/libclang_rt.asan_cxx-i386.a: No
>> such file or directory
>> clang-3.9: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>>
>> Has anyone seen this?
>>
>>
>> Thanks.  Diego.
>>
>
>


-- 
Alexey Samsonov
vonosmas at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160226/a4e8a1e0/attachment.html>


More information about the llvm-dev mailing list