public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/2] Straighten cross names
Date: Fri, 21 Sep 2018 13:00:56 +0300	[thread overview]
Message-ID: <203dd235-1908-2b94-929d-479a4cb5ed25@ilbers.de> (raw)
In-Reply-To: <20180911101605.21977-1-henning.schild@siemens.com>

Hi Henning,

I've rebased your series to the current 'next',
enabled CROSS_COMPILATION in local.conf and tried to build on my 
debian-stretch-amd64 host and ran
'bitbake multiconfig:qemuarm-stretch:isar-image-base'.

It failed with error log:

Log data follows:
| DEBUG: Executing shell function do_install_builddeps
| Get:1 file:/isar-apt isar InRelease
| Ign:1 file:/isar-apt isar InRelease
| Get:2 file:/isar-apt isar Release [3554 B]
| Get:2 file:/isar-apt isar Release [3554 B]
| Get:3 file:/isar-apt isar Release.gpg
| Ign:3 file:/isar-apt isar Release.gpg
| Reading package lists...
| build architecture "amd64" is unequal host architecture "armhf" in 
which case the package architecture must not be "all" (but "armhf" instead)
| WARNING: exit code 255 from a shell command.
| ERROR: Function failed: do_install_builddeps (log file is located at 
/home/myo/work/isar/src/isar/build/tmp/work/debian-stretch-armhf/libhello-0.1-98f2e41-r0/temp/log.do_install_builddeps.8379)

Could you please have a look on that?

Maxim.

On 9/11/18 1:16 PM, Henning Schild wrote:
> With the recent introduction of cross building we introduced confusing
> names in Isar. The following article describes how the names should be
> in Debian, which is probably what we should follow.
> 
> https://wiki.debian.org/CrossCompiling#Nomenclature
> 
> This series partially fixes the names. Applying it without changing the
> rest would probably just increase the confusion. I am still posting it
> as a starting point and to point out that there currently is a naming
> issue in Isar.
> 
> Henning Schild (2):
>    cross: use env variables instead of switches
>    build-kernel: fix the cross compile arch naming
> 
>   meta/classes/dpkg.bbclass                         |  8 ++++++--
>   meta/recipes-devtools/buildchroot/files/build.sh  |  2 +-
>   meta/recipes-devtools/buildchroot/files/common.sh | 13 -------------
>   meta/recipes-devtools/buildchroot/files/deps.sh   |  2 +-
>   meta/recipes-kernel/linux/files/build-kernel.sh   | 18 +++++++++---------
>   meta/recipes-kernel/linux/linux-custom.inc        |  4 ++--
>   6 files changed, 19 insertions(+), 28 deletions(-)
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

      parent reply	other threads:[~2018-09-21 10:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 10:16 Henning Schild
2018-09-11 10:16 ` [PATCH 1/2] cross: use env variables instead of switches Henning Schild
2018-09-21 12:55   ` [PATCHv2 " Henning Schild
2018-09-21 13:08     ` Henning Schild
2018-09-27  7:12       ` Maxim Yu. Osipov
2018-09-27  7:15         ` Jan Kiszka
2018-09-28 10:47         ` Henning Schild
2018-09-11 10:16 ` [PATCH 2/2] build-kernel: fix the cross compile arch naming Henning Schild
2018-09-11 12:10   ` Jan Kiszka
2018-09-11 12:20     ` Henning Schild
2018-09-21 10:00 ` Maxim Yu. Osipov [this message]

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=203dd235-1908-2b94-929d-479a4cb5ed25@ilbers.de \
    --to=mosipov@ilbers.de \
    --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