From: Henning Schild <henning.schild@siemens.com>
To: <isar-users@googlegroups.com>
Subject: Re: [PATCH] multistrap: do not ignore multistrap errors anymore
Date: Thu, 19 Oct 2017 18:40:17 +0200 [thread overview]
Message-ID: <20171019184017.44c11095@md1em3qc> (raw)
In-Reply-To: <20171019163659.15289-1-henning.schild@siemens.com>
On Thu, 19 Oct 2017 18:36:59 +0200
Henning Schild <henning.schild@siemens.com> wrote:
> Issue: Isar problems are often hard to debug and often enough you
> wonder why configscript.sh is not there. In that case the real
> problem always is in multistrap actually failing and Isar ignoring
> the return value.
>
> Change: Do not ignore the return value of multistrap anymore.
>
> Impact: Debugging should become much easier, the last error message
> will be the actual error message.
Whoever put that "|| true" there probably had a reason to do so. The
multistrap manpage says something about accumulating also warnings and
adding them up in the return value. That might be the reason for
ignoring the output of such an essential step.
However, i could just build an image with this patch applied.
Henning
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> meta-isar/recipes-core/images/isar-image-base.bb | 2 +-
> meta/recipes-devtools/buildchroot/buildchroot.bb | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta-isar/recipes-core/images/isar-image-base.bb
> b/meta-isar/recipes-core/images/isar-image-base.bb index
> 121b586..7e36e22 100644 ---
> a/meta-isar/recipes-core/images/isar-image-base.bb +++
> b/meta-isar/recipes-core/images/isar-image-base.bb @@ -55,7 +55,7 @@
> do_rootfs() { sudo mount -t proc none ${IMAGE_ROOTFS}/proc
>
> # Create root filesystem
> - sudo multistrap -a ${DISTRO_ARCH} -d "${IMAGE_ROOTFS}" -f
> "${WORKDIR}/multistrap.conf" || true
> + sudo multistrap -a ${DISTRO_ARCH} -d "${IMAGE_ROOTFS}" -f
> "${WORKDIR}/multistrap.conf"
> # Configure root filesystem
> sudo chroot ${IMAGE_ROOTFS} /${DISTRO_CONFIG_SCRIPT}
> ${MACHINE_SERIAL} ${BAUDRATE_TTY} \ diff --git
> a/meta/recipes-devtools/buildchroot/buildchroot.bb
> b/meta/recipes-devtools/buildchroot/buildchroot.bb index
> 452536f..3e5c0ac 100644 ---
> a/meta/recipes-devtools/buildchroot/buildchroot.bb +++
> b/meta/recipes-devtools/buildchroot/buildchroot.bb @@ -55,7 +55,7 @@
> do_build() { sudo mount -t proc none ${IMAGE_ROOTFS}/proc
> # Create root filesystem
> - sudo multistrap -a ${DISTRO_ARCH} -d "${BUILDCHROOT_DIR}" -f
> "${WORKDIR}/multistrap.conf" || true
> + sudo multistrap -a ${DISTRO_ARCH} -d "${BUILDCHROOT_DIR}" -f
> "${WORKDIR}/multistrap.conf"
> # Install package builder script
> sudo install -m 755 ${THISDIR}/files/build.sh ${BUILDCHROOT_DIR}
next prev parent reply other threads:[~2017-10-19 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 16:36 Henning Schild
2017-10-19 16:40 ` Henning Schild [this message]
2017-10-24 7:25 ` Alexander Smirnov
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=20171019184017.44c11095@md1em3qc \
--to=henning.schild@siemens.com \
--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