search for: configure_lit_site_cfg

...tal to command. CMake Error at lib/CMakeLists.txt:19 (set_target_properties): set_target_properties called with incorrect number of arguments. Call Stack (most recent call first): lib/asan/CMakeLists.txt:77 (add_clang_runtime_static_library) CMake Error at lib/asan/lit_tests/CMakeLists.txt:1 (configure_lit_site_cfg): Unknown CMake command "configure_lit_site_cfg". -- Configuring incomplete, errors occurred! I also tried placing it inside the LLVM tree in the "projects" subdir, to no avail (same error). Adding SET(CMAKE_MODULE_PATH ${PROJECT_SOURCE_DIR}/../../cmake/Modules) at the top of...

...ror at lib/CMakeLists.txt:19 (set_target_properties): > set_target_properties called with incorrect number of arguments. > Call Stack (most recent call first): > lib/asan/CMakeLists.txt:77 (add_clang_runtime_static_library) > CMake Error at lib/asan/lit_tests/CMakeLists.txt:1 > (configure_lit_site_cfg): > Unknown CMake command "configure_lit_site_cfg". > -- Configuring incomplete, errors occurred! > > I also tried placing it inside the LLVM tree in the "projects" subdir, > to no avail (same error). Adding > SET(CMAKE_MODULE_PATH ${PROJECT_SOURCE_DIR}/../....

...xt:19 (set_target_properties): >> set_target_properties called with incorrect number of arguments. >> Call Stack (most recent call first): >> lib/asan/CMakeLists.txt:77 (add_clang_runtime_static_**library) >> CMake Error at lib/asan/lit_tests/CMakeLists.**txt:1 >> (configure_lit_site_cfg): >> Unknown CMake command "configure_lit_site_cfg". >> -- Configuring incomplete, errors occurred! >> >> I also tried placing it inside the LLVM tree in the "projects" subdir, to >> no avail (same error). Adding >> SET(CMAKE_MODULE_PATH ${P...

...uot; which is not an existing directory. CMake Error: File c:/llvm/tools/clang/test/lit.site.cfg.in does not exist. CMake Error at cmake/modules/AddLLVM.cmake:252 (configure_file): configure_file Problem configuring file Call Stack (most recent call first): tools/clang/test/CMakeLists.txt:10 (configure_lit_site_cfg) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130402/90256668/attachment.html>

...debug info, and then run those programs under a debugger +# such as GDB or LLDB to verify the results. + +set(DEBUGINFO_TESTS_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}) +set(DEBUGINFO_TESTS_BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}) + +set(DEBUGINFO_TEST_DEPS + clang + FileCheck + count + not + ) + +configure_lit_site_cfg( + ${CMAKE_CURRENT_SOURCE_DIR}/lit.site.cfg.py.in + ${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg.py + MAIN_CONFIG + ${CMAKE_CURRENT_SOURCE_DIR}/lit.cfg.py + ) + +add_lit_testsuite(check-debuginfo "Running debug info integration tests" + ${CMAKE_CURRENT_BINARY_DIR} + DEPENDS ${DEBUGINFO...

...gt; + >> +set(DEBUGINFO_TESTS_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}) >> +set(DEBUGINFO_TESTS_BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}) >> + >> +set(DEBUGINFO_TEST_DEPS >> + clang >> + FileCheck >> + count >> + not >> + ) >> + >> +configure_lit_site_cfg( >> + ${CMAKE_CURRENT_SOURCE_DIR}/lit.site.cfg.py.in <http://lit.site.cfg.py.in/> >> + ${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg.py <http://lit.site.cfg.py/> >> + MAIN_CONFIG >> + ${CMAKE_CURRENT_SOURCE_DIR}/lit.cfg.py <http://lit.cfg.py/> >> + )...

...such as GDB or LLDB to verify the results. > + > +set(DEBUGINFO_TESTS_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}) > +set(DEBUGINFO_TESTS_BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}) > + > +set(DEBUGINFO_TEST_DEPS > + clang > + FileCheck > + count > + not > + ) > + > +configure_lit_site_cfg( > + ${CMAKE_CURRENT_SOURCE_DIR}/lit.site.cfg.py.in <http://lit.site.cfg.py.in/> > + ${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg.py <http://lit.site.cfg.py/> > + MAIN_CONFIG > + ${CMAKE_CURRENT_SOURCE_DIR}/lit.cfg.py <http://lit.cfg.py/> > + ) > + > +add_lit...

I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure