public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH] linux-custom: Add support for kernels >= 4.17
Date: Sun, 30 Sep 2018 18:55:16 +0200	[thread overview]
Message-ID: <3773d179-2e46-7f85-26e8-961a0e06341d@web.de> (raw)

From: Jan Kiszka <jan.kiszka@siemens.com>

Upstream changed deb-pkg, and it no longer spits out a debian.tar.gz
archive. Take the debian folder generated by deb-pkg instead.

A second change is required because upstream now sets the target package
architecture as well, but dpkg-gencontrol will not like this in a cross
environment (host != package arch). Trick it.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/recipes-kernel/linux/files/build-kernel.sh | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/files/build-kernel.sh b/meta/recipes-kernel/linux/files/build-kernel.sh
index 2cee28f..3f39d43 100644
--- a/meta/recipes-kernel/linux/files/build-kernel.sh
+++ b/meta/recipes-kernel/linux/files/build-kernel.sh
@@ -51,8 +51,14 @@ mkdir -p ${REPACK_DIR}
 mkdir -p ${REPACK_LINUX_IMAGE_DIR}
 mkdir -p ${REPACK_LINUX_HEADERS_DIR}
 
+cp -a debian ${REPACK_DIR}
+
+# dpkg-gencontrol performs cross-incompatible checks on the
+# Architecture field; trick it to accept the control file
+sed -i "s/Architecture: .*/Architecture: any/" ${REPACK_DIR}/debian/control
+
 cd ..
-tar xzf linux-${PV}_${PV}-1.debian.tar.gz -C ${REPACK_DIR}
+
 dpkg-deb -R linux-image-${PV}_${PV}-1_*.deb ${REPACK_LINUX_IMAGE_DIR}
 dpkg-deb -R linux-headers-${PV}_${PV}-1_*.deb ${REPACK_LINUX_HEADERS_DIR}
 
-- 
2.16.4

             reply	other threads:[~2018-09-30 16:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30 16:55 Jan Kiszka [this message]
2018-10-01  7:46 ` Maxim Yu. Osipov
2018-10-01  7:54   ` Jan Kiszka
2018-10-01  8:19     ` Jan Kiszka
2018-10-01  8:50       ` Jan Kiszka
2018-10-01  9:02         ` Maxim Yu. Osipov
2018-10-01 10:51 ` Maxim Yu. Osipov

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=3773d179-2e46-7f85-26e8-961a0e06341d@web.de \
    --to=jan.kiszka@web.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