public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Deepesh Varatharajan <deepesh.varatharajan@windriver.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"Sundeep.Kokkonda@windriver.com" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] [PATCH V4 1/2] rust: Use llvm instead of rust-llvm
Date: Tue, 14 Oct 2025 19:44:49 +0530	[thread overview]
Message-ID: <d34dff4b-bb0d-40b6-ab19-dffea7f575c9@windriver.com> (raw)
In-Reply-To: <512B27D3-F57A-40D3-84D9-30E529FE631D@arm.com>


On 13-10-2025 18:40, Ross Burton wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Hi Deepesh,
>
> On 10 Oct 2025, at 15:47, Varatharajan, Deepesh via lists.openembedded.org <deepesh.varatharajan=windriver.com@lists.openembedded.org> wrote:
>> +                  -DLLVM_INSTALL_UTILS=ON \
> Can you document what utility is needed here?
Sure
>
> Also I’ve asked our LLVM team if they have any feedback on how we’re using llvm-config.
>
> Cheers,
> Ross


      reply	other threads:[~2025-10-14 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 14:47 [PATCH V4 1/2] rust: Use llvm instead of rust-llvm Deepesh.Varatharajan
2025-10-10 14:47 ` [PATCH V4 2/2] rust: Drop rust-llvm Deepesh.Varatharajan
2025-10-12  7:55 ` [OE-core] [PATCH V4 1/2] rust: Use llvm instead of rust-llvm Mathieu Dubois-Briand
2025-10-13 13:10 ` Ross Burton
2025-10-14 14:14   ` Deepesh Varatharajan [this message]

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=d34dff4b-bb0d-40b6-ab19-dffea7f575c9@windriver.com \
    --to=deepesh.varatharajan@windriver.com \
    --cc=Ross.Burton@arm.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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