From: Christian Storm <christian.storm@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks
Date: Tue, 12 Dec 2017 09:04:31 +0100 [thread overview]
Message-ID: <20171212080431.rwidzbbb7utdwq7k@MD1KR9XC.ww002.siemens.net> (raw)
In-Reply-To: <b8384250-c0f7-35da-36f2-5a5ce1e4833a@ilbers.de>
> >>> ERROR: Nothing PROVIDES '${IMAGE_INSTALL}' (but
> >>> multiconfig:qemuamd64-stretch:/builder/isar/meta/recipes-devtools/buildchroot/buildchroot.bb
> >>> DEPENDS on or otherwise requires it)
> >
> > a 'IMAGE_INSTALL ?= ""' fixes that.
> >
>
> Thanks for this catch.
>
> It would be helpful if you describe your changes from upstream Isar that
> leads to this issue. Am I right, that you do not set IMAGE_INSTALL
> variable in local.conf file? Also an ideas how to handle such cases in
> pure Isar are welcome.
I sent a patch for exactly this on Thu, 7 Dec 2017 14:17:48 +0100 with
the subject "[PATCH] buildchroot: soft-assign default IMAGE_INSTALL".
Besten Gru�,
Christian
--
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany
next prev parent reply other threads:[~2017-12-12 8:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 10:25 [PATCH 0/4 v2] Buildchroot prepare/cleanup Alexander Smirnov
2017-11-23 10:25 ` [PATCH 1/4 v2] dpkg-base: Fix buildchroot dependancy Alexander Smirnov
2017-11-23 10:25 ` [PATCH 2/4 v2] image: Add do_rootfs template to image class Alexander Smirnov
2017-11-23 10:25 ` [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks Alexander Smirnov
2017-11-24 14:55 ` Henning Schild
2017-11-24 15:48 ` Alexander Smirnov
2017-11-24 16:34 ` Henning Schild
2017-11-24 16:51 ` Alexander Smirnov
2017-11-27 7:56 ` Henning Schild
2017-11-27 8:15 ` Alexander Smirnov
2017-12-08 7:58 ` Christian Storm
2017-12-11 9:23 ` Alexander Smirnov
2017-12-11 12:16 ` Henning Schild
2017-12-11 13:37 ` Storm, Christian (CT RDA ITP SES-DE)
2017-12-11 14:12 ` Alexander Smirnov
2017-12-11 15:14 ` Christian Storm
2017-12-12 7:39 ` Alexander Smirnov
2017-12-12 8:01 ` Christian Storm
2017-12-12 8:21 ` Alexander Smirnov
2017-12-11 11:32 ` Henning Schild
2017-12-11 18:29 ` Henning Schild
2017-12-11 19:56 ` Alexander Smirnov
2017-12-12 8:04 ` Christian Storm [this message]
2017-12-12 12:05 ` Henning Schild
2017-12-13 5:43 ` Jan Kiszka
2017-12-11 18:32 ` Henning Schild
2017-11-23 10:25 ` [PATCH 4/4 v2] dpkg-base: Update git alternates Alexander Smirnov
2017-11-24 14:57 ` Henning Schild
2017-11-24 15:12 ` Alexander Smirnov
2017-11-27 7:44 ` Henning Schild
2017-11-27 8:03 ` Alexander Smirnov
2017-11-27 15:42 ` Henning Schild
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=20171212080431.rwidzbbb7utdwq7k@MD1KR9XC.ww002.siemens.net \
--to=christian.storm@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