[llvm-dev] Upcoming change with how libc++, libc++abi and libunwind are being built

Louis Dionne via llvm-dev llvm-dev at lists.llvm.org
Mon Oct 18 13:18:56 PDT 2021

On Mon, Oct 18, 2021 at 2:49 PM Michael Kruse <llvmdev at meinersbur.de> wrote:

> Am Mo., 18. Okt. 2021 um 13:06 Uhr schrieb Louis Dionne <
> ldionne.2 at gmail.com>:
> > On Mon, Oct 18, 2021 at 12:23 PM Michael Kruse <llvmdev at meinersbur.de>
> wrote:
> > The build bots that wish to build libc++ with a supported
> non-clang-trunk compiler
> > can switch to the "default build", which is basically the equivalent of
> the Project
> > build we had before.
> Which buildbots will test the "default build" for gcc/AppleClang/Clang
> 11/Clang 12? Individual buildbot maintainers may be interested in
> keeping their buildbot green, not necessarily to ensure coverage.

Nowadays, we handle all libc++'s own build bots through BuildKite at

That pipeline contains all the configurations that we support officially.
If someone has a build bot and
they think they are adding coverage, we'd like to know it so we can look
into migrating it to BuildKite
and owning it ourselves.

Otherwise, they should just make whatever change is needed to keep their
bot green. In most cases I
would expect the easiest thing to do here would be to use the Bootstrapping
build so as to always build
against the latest Clang, however they can also use the "Default build"
with a suitably-recent system
compiler if they want to avoid building all of Clang on their bot.


> Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211018/084050f0/attachment.html>

More information about the llvm-dev mailing list