From: Henning Schild <henning.schild@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 0/2] Fix sid-ports riscv64 build
Date: Thu, 1 Sep 2022 10:21:24 +0200 [thread overview]
Message-ID: <20220901102124.31f71bae@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220901045201.9294-1-ubely@ilbers.de>
Am Thu, 1 Sep 2022 06:51:59 +0200
schrieb Uladzimir Bely <ubely@ilbers.de>:
> Sid-ports got newer version of binutils and this led to the broken
> native riscv64 builds for linux-mainline and opensbi-sifive-fu540.
>
> Here are backported patches from upstreams.
>
> Alternative solution would be upgrading version of the packages in
> Isar up to linux-mainline >= 5.17 and opensbi-sifive-fu540 >= 1.1.
I think that would be the better option. Why maintain those backports
and stay on old stuff?
Henning
>
> Uladzimir Bely (2):
> linux-mainline: Fix riscv64 build with binutils 2.38
> opensbi-sifive-fu540: Fix build with binutils 2.38
>
> ...akefile-fix-build-with-binutils-2.38.patch | 58
> +++++++++++++++++++ .../opensbi/opensbi-sifive-fu540_0.9.bb |
> 1 + ...1-riscv-fix-build-with-binutils-2.38.patch | 50
> ++++++++++++++++ .../linux/linux-mainline_5.4.70.bb | 2 +
> 4 files changed, 111 insertions(+)
> create mode 100644
> meta-isar/recipes-bsp/opensbi/files/0001-Makefile-fix-build-with-binutils-2.38.patch
> create mode 100644
> meta-isar/recipes-kernel/linux/files/0001-riscv-fix-build-with-binutils-2.38.patch
>
prev parent reply other threads:[~2022-09-01 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 4:51 Uladzimir Bely
2022-09-01 4:52 ` [PATCH 1/2] linux-mainline: Fix riscv64 build with binutils 2.38 Uladzimir Bely
2022-09-01 11:26 ` Jan Kiszka
2022-09-01 4:52 ` [PATCH 2/2] opensbi-sifive-fu540: Fix " Uladzimir Bely
2022-09-01 11:21 ` Jan Kiszka
2022-09-01 8:21 ` Henning Schild [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=20220901102124.31f71bae@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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