From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 3/3] lldb: add new recipe, split out of clang
Date: Tue, 15 Jul 2025 10:25:41 +0200 [thread overview]
Message-ID: <DBCHHHGNABHB.3CT26KMMAQ0TW@bootlin.com> (raw)
In-Reply-To: <20250711155136.2172651-3-ross.burton@arm.com>
On Fri Jul 11, 2025 at 5:51 PM CEST, Ross Burton via lists.openembedded.org wrote:
> LLDB takes a reasonable amount of time to compile, but also isn't an
> essential component of the LLVM suite.
>
> Instead of always building it when we build clang, split it out into a
> separate recipe.
>
> On my build machine where clang takes 21 minutes to build with lldb, it
> takes 19 minutes without lldb.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
Hi Ross,
I know you are already aware of this, but just to keep a trace, this is
failing reproducibility test on the autobuilder.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2088
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20250714-7q8vsabu/packages/diff-html/
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-15 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 15:51 [PATCH 1/3] clang: move BPN assignment from common.inc Ross Burton
2025-07-11 15:51 ` [PATCH 2/3] llvm-tblgen-native: add new recipe Ross Burton
2025-07-11 16:02 ` Patchtest results for " patchtest
2025-07-11 16:35 ` [OE-core] " Khem Raj
2025-07-11 17:14 ` Ross Burton
2025-07-11 15:51 ` [PATCH 3/3] lldb: add new recipe, split out of clang Ross Burton
2025-07-11 16:02 ` Patchtest results for " patchtest
2025-07-11 16:32 ` [OE-core] " Khem Raj
2025-07-15 8:25 ` Mathieu Dubois-Briand [this message]
2025-07-11 16:00 ` [OE-core] [PATCH 1/3] clang: move BPN assignment from common.inc Marko, Peter
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=DBCHHHGNABHB.3CT26KMMAQ0TW@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/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