From: Miguel Ojeda <ojeda@kernel.org>
To: Christian Schrrefl <chrisi.schrefl@gmail.com>
Cc: naresh.kamboju@linaro.org,
Russell King <rmk+kernel@armlinux.org.uk>,
Rudraksha Gupta <guptarud@gmail.com>,
Alice Ryhl <aliceryhl@google.com>,
Ard Biesheuvel <ardb@kernel.org>,
anders.roxell@linaro.org, arnd@arndb.de,
dan.carpenter@linaro.org, laura.nao@collabora.com,
linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
regressions@lists.linux.dev, rust-for-linux@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: Build: arm rustgcc unknown argument '-mno-fdpic'
Date: Mon, 7 Apr 2025 20:37:16 +0200 [thread overview]
Message-ID: <20250407183716.796891-1-ojeda@kernel.org> (raw)
In-Reply-To: <CA+G9fYvOanQBYXKSg7C6EU30k8sTRC0JRPJXYu7wWK51w38QUQ@mail.gmail.com>
On Mon, 07 Apr 2025 22:58:02 +0530 Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Regressions on arm build with config rustgcc-lkftconfig-kselftest on the
> Linux mainline and next failed with CONFIG_RUST=y enabled.
> Bad: next-20250327
> Good: next-20250326
> Unable to generate bindings: clang diagnosed error: error: unknown
> argument: '-mno-fdpic'
I assume this is the arm support, i.e. commit ccb8ce526807 ("ARM: 9441/1:
rust: Enable Rust support for ARMv7").
Clang does not seem to support `-mno-fdpic`, thus you probably need to add it to
`bindgen_skip_c_flags` in `rust/Makefile` so that it gets skipped when the C
compiler is GCC.
If you do so, please double-check if the flag could potentially alter the ABI in
a way that `bindgen` would generate the wrong bindings.
I hope that helps!
Cheers,
Miguel
next prev parent reply other threads:[~2025-04-07 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 17:28 Build: arm rustgcc unknown argument '-mno-fdpic' Naresh Kamboju
2025-04-07 18:37 ` Miguel Ojeda [this message]
2025-04-15 11:40 ` Naresh Kamboju
2025-04-15 15:38 ` Miguel Ojeda
2025-04-18 19:44 ` Ben Wolsieffer
2025-04-18 22:30 ` Miguel Ojeda
2025-04-24 13:39 ` Ben Wolsieffer
2025-04-24 17:01 ` Miguel Ojeda
2025-05-20 23:21 ` Rudraksha Gupta
2025-05-21 6:49 ` Miguel Ojeda
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=20250407183716.796891-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=aliceryhl@google.com \
--cc=anders.roxell@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=chrisi.schrefl@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=guptarud@gmail.com \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rust-for-linux@vger.kernel.org \
--cc=torvalds@linux-foundation.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