From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH] Adjust do_apt_fetch dependency to crossbuild
Date: Mon, 16 Sep 2019 23:37:58 +0200 [thread overview]
Message-ID: <402461c9-e17e-699e-b415-8bbde608cb72@siemens.com> (raw)
In-Reply-To: <20190916211942.uvcykv4qonibfaz5@yssyq.m.ilbers.de>
On 16.09.19 23:19, Baurzhan Ismagulov wrote:
> On Mon, Sep 16, 2019 at 10:58:42PM +0200, Jan Kiszka wrote:
>> Which target exactly fails? Just tried one successfully, and we are also
>> using the very same pattern that hello_2.10.bb and hello.inc implement in
>> production for other packages.
>
> It succeeds for amd64 and arm64, and fails for de0-nano-soc-stretch:
>
> egrep -n " bitbake |hello-2.10-r0: task do_apt_fetch|Running task.*hello-isar.bb:do_apt_fetch" log
> 134:+ bitbake multiconfig:qemuarm-stretch:isar-image-base multiconfig:qemuarm-buster:isar-image-base multiconfig:qemuarm-bullseye:isar-image-base multiconfig:qemuarm64-stretch:isar-image-base multiconfig:qemuamd64-stretch:isar-image-base multiconfig:de0-nano-soc-stretch:isar-image-base multiconfig:rpi-stretch:isar-image-base
> 826:NOTE: recipe hello-2.10-r0: task do_apt_fetch: Started
> 838:NOTE: Running task 314 of 896 (multiconfig:qemuamd64-stretch:/workspace/build/isar_ibr_devel_fast/10/meta-isar/recipes-app/hello-isar/hello-isar.bb:do_apt_fetch)
> 840:NOTE: recipe hello-2.10-r0: task do_apt_fetch: Succeeded
> 1295:NOTE: Running task 483 of 896 (multiconfig:qemuarm64-stretch:/workspace/build/isar_ibr_devel_fast/10/meta-isar/recipes-app/hello-isar/hello-isar.bb:do_apt_fetch)
> 1308:NOTE: recipe hello-2.10-r0: task do_apt_fetch: Started
> 1344:NOTE: recipe hello-2.10-r0: task do_apt_fetch: Succeeded
> 1420:NOTE: recipe hello-2.10-r0: task do_apt_fetch: Started
> 1439:NOTE: recipe hello-2.10-r0: task do_apt_fetch: Failed
> 1441:NOTE: Running task 532 of 896 (multiconfig:de0-nano-soc-stretch:/workspace/build/isar_ibr_devel_fast/10/meta-isar/recipes-app/hello-isar/hello-isar.bb:do_apt_fetch)
>
Sharing issue, similar to linux-libc-dev: Once you deployed a self-built version
of hello that matches this build, apt will try to pull the sources of that
higher prioritized isar-apt version, rather than from upstream. Not sure if we
can easily define that "apt://" excludes isar-apt, but that would solve this. It
probably also makes sense.
Consequently, building only de0-nano-soc-stretch:hello in a clean built env
works fine.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-09-16 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 10:38 Jan Kiszka
2019-09-12 13:49 ` Baurzhan Ismagulov
2019-09-13 6:22 ` Jan Kiszka
2019-09-16 20:46 ` Baurzhan Ismagulov
2019-09-16 20:58 ` Jan Kiszka
2019-09-16 21:19 ` Baurzhan Ismagulov
2019-09-16 21:37 ` Jan Kiszka [this message]
2019-09-17 8:51 ` 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=402461c9-e17e-699e-b415-8bbde608cb72@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=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