From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 0/2] Fix riscv64/trixie build
Date: Fri, 11 Apr 2025 13:15:36 +0300 [thread overview]
Message-ID: <20250411101752.16954-1-ubely@ilbers.de> (raw)
NoCrossTest.test_nocross_sid test is failing in CI for some time
due to recent Debian Trixie updates.
Backport linux and u-boot upstream patches that solve build issues.
Changes since v1:
- Correct patch 2 commit message where wrong branch was mentioned.
Uladzimir Bely (2):
u-boot-starfive-visionfive2: Fix build with swig 4.3.0
linux-starfive: Fix build with GNU make 4.4
...bfdt-libfdt.i_shipped-Use-SWIG_Appen.patch | 60 +++++++++++++++++++
.../u-boot-starfive-visionfive2_2024.01.bb | 1 +
...ogue-fix-build-issue-on-GNU-Make-4.4.patch | 29 +++++++++
.../linux-starfive_6.6.20-visionfive2.bb | 1 +
4 files changed, 91 insertions(+)
create mode 100644 meta-isar/recipes-bsp/u-boot/files/0001-scripts-dtc-pylibfdt-libfdt.i_shipped-Use-SWIG_Appen.patch
create mode 100644 meta-isar/recipes-kernel/linux/files/0001-drm-img-rogue-fix-build-issue-on-GNU-Make-4.4.patch
--
2.49.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20250411101752.16954-1-ubely%40ilbers.de.
next reply other threads:[~2025-04-11 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 10:15 Uladzimir Bely [this message]
2025-04-11 10:15 ` [PATCH v2 1/2] u-boot-starfive-visionfive2: Fix build with swig 4.3.0 Uladzimir Bely
2025-04-11 10:15 ` [PATCH v2 2/2] linux-starfive: Fix build with GNU make 4.4 Uladzimir Bely
2025-04-15 7:02 ` [PATCH v2 0/2] Fix riscv64/trixie build Uladzimir Bely
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=20250411101752.16954-1-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox