public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Claudius Heine <ch@denx.de>, Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 0/4] Rework isar-apt
Date: Thu, 1 Feb 2018 22:37:07 +0300	[thread overview]
Message-ID: <c6a902a7-d946-a266-9086-6e30db13ec5c@ilbers.de> (raw)
In-Reply-To: <1517510238.2646.18.camel@denx.de>



On 02/01/2018 09:37 PM, Claudius Heine wrote:
> Hi,
> 
> On Thu, 2018-02-01 at 17:25 +0100, Jan Kiszka wrote:
>> On 2018-02-01 17:22, Alexander Smirnov wrote:
>>> On 02/01/2018 07:14 PM, Jan Kiszka wrote:
>>>> On 2018-02-01 12:29, Alexander Smirnov wrote:
>>>>> Hi all,
>>>>>
>>>>> this series intended to make buildchroot able to work with
>>>>> isar-apt.
>>>>> I've tried to add extended comments to each patch.
>>>>>
>>>>> Impact: with this series I'm able to build 'example-hello' <->
>>>>> 'libhello'
>>>>> without any hacks. So the deps are installed automatically.
>>>>>
>>>>> NOTE: I've migrated to bitbake [lockfiles] mechanism, don't
>>>>> know how
>>>>> robust it
>>>>> is, but build in the loop started in the evening didn't fail
>>>>> during
>>>>> the night.
>>>>>
>>>>
>>>> I can happily report: It works as promised also for my use case
>>>> (jailhouse.bb -> linux-jailhouse.bb, both Isar-built).
>>>>
>>>
>>> Thanks! But I've found an issue with events. :-( Our bitbake didn't
>>> handle them for multiconfig, the following patch seems to add this:
>>>
>>> https://patchwork.openembedded.org/patch/141626/
>>>
>>> Events is very good mechanism to clean up Isar build from pending
>>> mounts
>>> without headache with build fails, so I think it would be valuable
>>> to
>>> try latest bitbake. I'll report the results as soon as build
>>> finishes.
>>
>> Perfect: Claudius just told me we need to update bitbake anyway to
>> have
>> proper multiconfig support (i.e. no more hacky copying of files
>> during
>> isar-init-build-env). Claudius, which version at least?
> 
> I haven't tested it but I think its this one:
> 
> http://git.openembedded.org/bitbake/commit/?id=518b9015c2be8d3894277a8e
> 54890d6f04d656c0
> 

The following patch is needed for latest bitbake (derived from Yocto):

diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-bitbake.conf
index 10cd45d..b853c88 100644
--- a/meta/conf/isar-bitbake.conf
+++ b/meta/conf/isar-bitbake.conf
@@ -28,5 +28,6 @@ BUILDCHROOT_DIR = 
"${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot/rootfs"
  BB_SIGNATURE_HANDLER ?= "noop"

  include conf/local.conf
+include conf/multiconfig/${BB_CURRENT_MC}.conf
  include conf/machine/${MACHINE}.conf
  include conf/distro/${DISTRO}.conf

Alex

  reply	other threads:[~2018-02-01 19:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 11:29 Alexander Smirnov
2018-02-01 11:29 ` [PATCH 1/4] isar-apt: Introduce separate recipe Alexander Smirnov
2018-02-01 11:29 ` [PATCH 2/4] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-04 12:06   ` Jan Kiszka
2018-02-01 11:29 ` [PATCH 3/4] build.sh: Update apt sources Alexander Smirnov
2018-02-01 11:40   ` Jan Kiszka
2018-02-01 11:48     ` Alexander Smirnov
2018-02-01 13:13       ` Jan Kiszka
2018-02-01 13:43         ` Alexander Smirnov
2018-02-01 14:28           ` Jan Kiszka
2018-02-01 11:29 ` [PATCH 4/4] build.sh: Force 'yes' for apt Alexander Smirnov
2018-02-01 11:41   ` Jan Kiszka
2018-02-01 12:27     ` Alexander Smirnov
2018-02-01 16:14 ` [PATCH 0/4] Rework isar-apt Jan Kiszka
2018-02-01 16:22   ` Alexander Smirnov
2018-02-01 16:25     ` Jan Kiszka
2018-02-01 16:54       ` Alexander Smirnov
2018-02-01 17:03         ` Jan Kiszka
2018-02-01 20:32           ` Alexander Smirnov
2018-02-01 18:37       ` Claudius Heine
2018-02-01 19:37         ` Alexander Smirnov [this message]
2018-02-01 20:09           ` Claudius Heine
2018-02-01 20:13             ` Claudius Heine

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=c6a902a7-d946-a266-9086-6e30db13ec5c@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=ch@denx.de \
    --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