From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Daniel Lang <dalang@gmx.at>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1, next] package/llvm-project/compiler-rt: fix build with Ninja
Date: Tue, 8 Aug 2023 11:20:16 +0200 [thread overview]
Message-ID: <20230808112016.226ac8be@windsurf> (raw)
In-Reply-To: <20230808090407.558957-1-thomas@devoogdt.com>
On Tue, 8 Aug 2023 11:04:07 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> ninja: error: dependency cycle: include/sanitizer/allocator_interface.h -> include/sanitizer/allocator_interface.h
>
> It's not clear why this cycle happens, but compiler-rt also proposes to
> create a separate build folder on their site: https://compiler-rt.llvm.org/.
>
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
Not sure to understand: the default backend for CMake is still
makefiles, and compiler-rt was not switched to using ninja. So?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-08 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:04 [Buildroot] [PATCH v1, next] package/llvm-project/compiler-rt: fix build with Ninja Thomas Devoogdt
2023-08-08 9:20 ` Thomas Petazzoni via buildroot [this message]
2023-08-08 11:22 ` Thomas Devoogdt
2023-08-08 14:23 ` Thomas Petazzoni via buildroot
2023-08-08 18:02 ` Yann E. MORIN
2023-08-14 6:36 ` [Buildroot] [PATCH v2, next] package/llvm-project/compiler-rt: fix circular dependency warning Thomas Devoogdt
2023-08-14 11:23 ` Yann E. MORIN
2023-09-12 18:28 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230808112016.226ac8be@windsurf \
--to=buildroot@buildroot.org \
--cc=dalang@gmx.at \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.com \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox