From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-custom: Update isar-apt prior to installing build deps
Date: Tue, 6 Nov 2018 12:49:10 +0100 [thread overview]
Message-ID: <20181106124910.66f51096@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <8cc02aa9-ad5a-0190-0162-fcb648b50d82@siemens.com>
Am Tue, 6 Nov 2018 12:23:53 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> Some of them may have been built by a recipe.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> Henning, maybe also useful for your scenario of the openssl rebuild
> because the kernel depends on self-built packages there as well.
Will try once merged.
> meta/recipes-kernel/linux/linux-custom.inc | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc
> b/meta/recipes-kernel/linux/linux-custom.inc index e9a68fd..d9b2935
> 100644 --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -27,11 +27,18 @@ KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools |
> linux-initramfs-tool, kmod, linux-ba KERNEL_HEADERS_DEBIAN_DEPENDS ?=
> "libc6, libssl1.1"
> do_install_builddeps() {
> + dpkg_do_mounts
> E="${@ bb.utils.export_proxies(d)}"
> + sudo -E chroot ${BUILDCHROOT_DIR} \
> + apt-get update \
> + -o
> Dir::Etc::sourcelist="sources.list.d/isar-apt.list" \
> + -o Dir::Etc::sourceparts="-" \
> + -o APT::Get::List-Cleanup="0"
All these args make sure we just update that one repo?
Henning
> sudo -E chroot ${BUILDCHROOT_DIR} \
> apt-get install \
> -y -o Debug::pkgProblemResolver=yes \
> --no-install-recommends ${KBUILD_DEPENDS}
> + dpkg_undo_mounts
> }
>
> addtask install_builddeps after do_prepare_build before do_build
next prev parent reply other threads:[~2018-11-06 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 11:23 Jan Kiszka
2018-11-06 11:49 ` Henning Schild [this message]
2018-11-06 12:00 ` Jan Kiszka
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=20181106124910.66f51096@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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