All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: openembedded-core@lists.openembedded.org, yogesh.tyagi@intel.com
Cc: raj.khem@gmail.com
Subject: Re: [OE-core] [PATCH] bindgen-cli: set CLANG_PATH in native wrapper to native clang
Date: Wed, 08 Jul 2026 05:41:32 -0700 (PDT)	[thread overview]
Message-ID: <6a4e457c.dfaa6ae2.334193.82f9@mx.google.com> (raw)
In-Reply-To: <20260630190004.1083997-1-yogesh.tyagi@intel.com>

On Tue, Jul 1, 2026, Yogesh Tyagi wrote:
> Set CLANG_PATH to the native clang in the bindgen wrapper so clang-sys
> uses the runnable host binary first, short-circuiting the llvm-config
> lookup. The native wrapper already exports LIBCLANG_PATH the same way.

The reasoning is sound, and beyond the mesa rusticl case this also helps
the rust-in-kernel build: kernel-yocto-rust.bbclass pulls in both
clang-native and bindgen-cli-native, so native bindgen can hit the same
target-clang-via-llvm-config lookup. Pinning CLANG_PATH to the native
clang that matches the native libclang is the consistent thing to do
there too, so:

Reviewed-by: Bruce Ashfield <bruce.ashfield@gmail.com>

One thing while you're here: the recipe is BBCLASSEXTEND = "native
nativesdk", but the wrapper fix is do_install:append:class-native() only.
Unless I'm misreading it, that leaves the nativesdk bindgen wrapper with
just LIBCLANG_PATH and no CLANG_PATH, so an SDK that runs bindgen (e.g.
rust kernel-module development in the SDK, which is being wired up
separately) would still hit the identical "could not run executable
.../clang-NN" failure. If that's right, could you extend the CLANG_PATH
export to the nativesdk wrapper as well? A shared helper (or a
class-native/class-nativesdk pair pointing at the respective
STAGING_BINDIR) would cover both. If nativesdk is already handled some
other way, ignore me.

Bruce


  reply	other threads:[~2026-07-08 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 19:00 [PATCH] bindgen-cli: set CLANG_PATH in native wrapper to native clang yogesh.tyagi
2026-07-08 12:41 ` Bruce Ashfield [this message]
2026-07-09  6:28   ` [OE-core] " Böszörményi Zoltán
2026-07-11 15:44   ` Tyagi, Yogesh
2026-07-12  5:43 ` [PATCH v2] bindgen-cli: set CLANG_PATH in native and nativesdk wrappers to matching clang yogesh.tyagi
     [not found] <18BDF101D1878987.114350@lists.openembedded.org>
2026-07-08  6:23 ` [OE-core] [PATCH] bindgen-cli: set CLANG_PATH in native wrapper to native clang Tyagi, Yogesh

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=6a4e457c.dfaa6ae2.334193.82f9@mx.google.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=yogesh.tyagi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.