From: Geert Stappers <stappers@stappers.nl>
To: Christian Schrefl <chrisi.schrefl@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
rust-for-linux@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Jamie Cunliffe <Jamie.Cunliffe@arm.com>,
Sven Van Asbroeck <thesven73@gmail.com>
Subject: Re: [PATCH 1/1] arm: rust: Enable Rust support for ARMv7
Date: Sat, 8 Jun 2024 14:42:59 +0200 [thread overview]
Message-ID: <ZmRR0yuqgVd50xXL@gpm.stappers.nl> (raw)
In-Reply-To: <4e0f5932-c7bc-4878-862c-1186cbecd71d@gmail.com>
On Sat, Jun 08, 2024 at 12:30:12AM +0200, Christian Schrefl wrote:
> --- a/rust/Makefile
> +++ b/rust/Makefile
> @@ -286,7 +286,8 @@ bindgen_skip_c_flags := -mno-fp-ret-in-387 -mpreferred-stack-boundary=% \
>
> # Derived from `scripts/Makefile.clang`.
> BINDGEN_TARGET_x86 := x86_64-linux-gnu
> -BINDGEN_TARGET_arm64 := aarch64-linux-gnu
> +BINDGEN_TARGET_arm64:= aarch64-linux-gnu
That white space change is probably accidently.
> +BINDGEN_TARGET_arm := arm-linux-gnueabi
> BINDGEN_TARGET := $(BINDGEN_TARGET_$(SRCARCH))
>
> # All warnings are inhibited since GCC builds are very experimental,
Groeten
Geert Stappers
--
Silence is hard to parse
WARNING: multiple messages have this Message-ID (diff)
From: Geert Stappers <stappers@stappers.nl>
To: Christian Schrefl <chrisi.schrefl@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
rust-for-linux@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Jamie Cunliffe <Jamie.Cunliffe@arm.com>,
Sven Van Asbroeck <thesven73@gmail.com>
Subject: Re: [PATCH 1/1] arm: rust: Enable Rust support for ARMv7
Date: Sat, 8 Jun 2024 14:42:59 +0200 [thread overview]
Message-ID: <ZmRR0yuqgVd50xXL@gpm.stappers.nl> (raw)
In-Reply-To: <4e0f5932-c7bc-4878-862c-1186cbecd71d@gmail.com>
On Sat, Jun 08, 2024 at 12:30:12AM +0200, Christian Schrefl wrote:
> --- a/rust/Makefile
> +++ b/rust/Makefile
> @@ -286,7 +286,8 @@ bindgen_skip_c_flags := -mno-fp-ret-in-387 -mpreferred-stack-boundary=% \
>
> # Derived from `scripts/Makefile.clang`.
> BINDGEN_TARGET_x86 := x86_64-linux-gnu
> -BINDGEN_TARGET_arm64 := aarch64-linux-gnu
> +BINDGEN_TARGET_arm64:= aarch64-linux-gnu
That white space change is probably accidently.
> +BINDGEN_TARGET_arm := arm-linux-gnueabi
> BINDGEN_TARGET := $(BINDGEN_TARGET_$(SRCARCH))
>
> # All warnings are inhibited since GCC builds are very experimental,
Groeten
Geert Stappers
--
Silence is hard to parse
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-06-08 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 22:30 [PATCH 1/1] arm: rust: Enable Rust support for ARMv7 Christian Schrefl
2024-06-07 22:30 ` Christian Schrefl
2024-06-08 12:16 ` Miguel Ojeda
2024-06-08 12:16 ` Miguel Ojeda
2024-06-08 13:57 ` Christian Schrefl
2024-06-08 13:57 ` Christian Schrefl
2024-06-08 12:42 ` Geert Stappers [this message]
2024-06-08 12:42 ` Geert Stappers
2024-06-10 19:00 ` Andrew Lunn
2024-06-10 19:00 ` Andrew Lunn
2024-06-10 19:37 ` Christian Schrefl
2024-06-10 19:37 ` Christian Schrefl
2024-06-10 21:19 ` Miguel Ojeda
2024-06-10 21:19 ` 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=ZmRR0yuqgVd50xXL@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=Jamie.Cunliffe@arm.com \
--cc=chrisi.schrefl@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=thesven73@gmail.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.