From: Vivian Wang <wangruikang@iscas.ac.cn>
To: "Asuna Yang" <spriteovo@gmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Jonathan Corbet" <corbet@lwn.net>,
"Jason Montleon" <jmontleo@redhat.com>,
"Han Gao" <rabenda.cn@gmail.com>,
"Conor Dooley" <conor@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v5 3/4] rust: add a Kconfig function to test for support of bindgen options
Date: Sun, 7 Dec 2025 02:16:43 +0800 [thread overview]
Message-ID: <35bacd20-c7e8-4a3f-be79-aa52701fc257@iscas.ac.cn> (raw)
In-Reply-To: <9687109b-dc93-4535-848c-e5f22aeb8e9d@gmail.com>
On 12/4/25 20:33, Asuna Yang wrote:
> On 12/4/25 5:06 PM, Vivian Wang wrote:
>
>>> +
>>> +# $(bindgen-backend-option,<flag>)
>>> +# Return y if bindgen backend supports <flag>, n otherwise
>>> +# For now, the backend refers only to libclang, so more
>>> specifically, this function tests whether the given flag is
>>> recognized by the libclang used by bindgen.
>>> +bindgen-backend-option = $(success,trap "rm -f .tmp_$$.h" EXIT;
>>> touch .tmp_$$.h; $(BINDGEN) .tmp_$$.h -- --target=$(BINDGEN_TARGET)
>>> $(1))
>>>
>> Can probably be simplified down to:
>>
>> $(BINDGEN) /dev/null -- -x c --target=$(BINDGEN_TARGET) $(1)
>>
>
> bindgen is sensitive to file extensions. If the file is not .h or
> .hpp, it complains:
>
> panicked at bindgen/ir/context.rs:562:15:
> libclang error; possible causes include:
> - Invalid flag syntax
> - Unrecognized flags
> - Invalid flag arguments
> - File I/O errors
> - Host vs. target architecture mismatch
That's so weird... I can't reproduce this if i pass -x c to bindgen,
like this:
$ bindgen --version
bindgen 0.72.1
$ bindgen /dev/null
panicked at /build/rust-bindgen-unwrapped-0.72.1-vendor/bindgen-0.72.1/ir/context.rs:562:15:
libclang error; possible causes include:
- Invalid flag syntax
- Unrecognized flags
- Invalid flag arguments
- File I/O errors
- Host vs. target architecture mismatch
If you encounter an error missing from this list, please file an issue or a PR!
$ bindgen /dev/null -- -x c
Failed to run rustfmt: No such file or directory (os error 2) (non-fatal, continuing)
/* automatically generated by rust-bindgen 0.72.1 */
The -x argument should explicitly tell (lib)clang what language the file
is without needing an extension. I don't know why it's not working for
you...
next prev parent reply other threads:[~2025-12-06 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 7:54 [PATCH v5 0/4] EDITME: RISC-V: re-enable gcc + rust builds Asuna Yang
2025-12-04 7:54 ` [PATCH v5 1/4] rust: export BINDGEN_TARGET from a separate Makefile Asuna Yang
2025-12-04 7:54 ` [PATCH v5 2/4] rust: generate a fatal error if BINDGEN_TARGET is undefined Asuna Yang
2025-12-04 12:41 ` Asuna Yang
2025-12-04 7:54 ` [PATCH v5 3/4] rust: add a Kconfig function to test for support of bindgen options Asuna Yang
2025-12-04 9:06 ` Vivian Wang
2025-12-04 12:33 ` Asuna Yang
2025-12-06 18:16 ` Vivian Wang [this message]
2025-12-06 23:41 ` Asuna Yang
2025-12-04 7:54 ` [PATCH v5 4/4] RISC-V: handle extension configs for bindgen, re-enable gcc + rust builds Asuna Yang
2025-12-04 8:26 ` [PATCH v5 0/4] EDITME: RISC-V: " Asuna Yang
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=35bacd20-c7e8-4a3f-be79-aa52701fc257@iscas.ac.cn \
--to=wangruikang@iscas.ac.cn \
--cc=a.hindborg@kernel.org \
--cc=alex@ghiti.fr \
--cc=aliceryhl@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jmontleo@redhat.com \
--cc=justinstitt@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=spriteovo@gmail.com \
--cc=tmgross@umich.edu \
/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;
as well as URLs for NNTP newsgroup(s).