[libc-dev] `ninja check-libc` : target does not exist on Windows

Siva Chandra via libc-dev libc-dev at lists.llvm.org
Mon Sep 27 11:50:48 PDT 2021

The requirements for libc on Windows are similar to libcxx on Windows. As
in, you have to additionally pass -DLLVM_FORCE_BUILD_RUNTIME=libc to cmake
and we need clang-cl to build. Also, it currently only works for Windows on
x86_64. The full instructions on how to get it working on Windows are
available here:

We used to have a bot connected to staging, but I just went looking for it
and it has vanished. Very likely it was lost during the outage from a few
weeks back. I will work on bringing it back up and hook it up to the
production master soon.

Siva Chandra

On Mon, Sep 27, 2021 at 11:24 AM Mehdi AMINI via libc-dev <
libc-dev at lists.llvm.org> wrote:

> Hi,
> We configured Phabricator pre-merge testing to be more fine grain in
> selecting the tests to run.
> As such when a patch touches libc, it'll try to run `ninja check-libc`
> instead of `check-all`. This works well on linux, but somehow it does
> not on Windows.
> Here is one log for example:
> https://buildkite.com/llvm-project/premerge-checks/builds/58009
> The libc project is correctly enabled in CMake:
> -- libc project is enabled
> But then it fails with:
> ninja: error: unknown target 'check-libc', did you mean 'check-lit'?
> Does anyone know why? I can find anything Windows specific in the
> various CMakeLists.txt in the libc folder of the repo.
> thanks,
> --
> Mehdi
> _______________________________________________
> libc-dev mailing list
> libc-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/libc-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/libc-dev/attachments/20210927/61e683f0/attachment.html>

More information about the libc-dev mailing list