From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6579174846558633984 X-Received: by 2002:aa7:d301:: with SMTP id p1-v6mr3451995edq.2.1532328948514; Sun, 22 Jul 2018 23:55:48 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:aa7:d7c9:: with SMTP id e9-v6ls4148407eds.7.gmail; Sun, 22 Jul 2018 23:55:48 -0700 (PDT) X-Google-Smtp-Source: AAOMgpciGmVRh9jGOFIAF+wZGyX+z9HdH0oOiVMTbZZcwLSwbuhbvcflmkAFJVNjgZM4TCl58u2P X-Received: by 2002:aa7:c48c:: with SMTP id m12-v6mr3454416edq.11.1532328948028; Sun, 22 Jul 2018 23:55:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532328947; cv=none; d=google.com; s=arc-20160816; b=D7LnqoLhiJdwxEz3F79CZUTRUPe96BXhxr/7MLzX30h0weYwWOIlkRz7D91psZZ8Y2 Zc85TnWaeZ1/UsNj57ad67NUBRtOmOZXa5X/ojRzaL8Z4mtjBdlkttNlVNLbTa+l3PnI ujIcSbLqGAOdGuwLo+J4mZwTVpLXoR8c5m0l6i0bfZrglrTVCC54reuewEZgvJZonEu7 JKHNLRGUxDQJfut/RsDl3jsi8Tme5Qp37ZQN9F6aXfcck7+Eeg5FTIt35SSDI+49lhmP z7E5sDnOgzM2TCcLjaDvwdYqjUMI2awC7S6WLGINxaXTSM4IkAlDP3WuTQUmtCqg8u0P /cFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:references:to:from:subject :arc-authentication-results; bh=3IemKBH55vEWgtaTZUzE7oTD2gMA1a67BZnOeEvKuR4=; b=pa8/gh+d2qGolN1SeFK1rt3ilNdmqnM2F19kZlaDuHsH28OrZF8f77nfyS3QZ6i0t+ oWtgw/bDr4aKOVuI4tWDFErdChrsXHK762sj+EiG8lcB35ZRDNkeOxRnwlX+fwMZpI2t HIargxnCYPSVz0IxnlnGsGrq2f7bGVqmL7hYRXdCxoEuSECBMzEfKn2EXRLc1b2q8O8k 3VuMUAKgxspC7uAP/HF2npdl67PQ2y0UWD/xyZO1oVaSMZqSbIZmM9hJWQbfqTQ5wpzG 9v4XUtmaaNZmMO8NPeiUKYcRpR7gdRm12RpwZoGSzQcisuWGw88cDhQm54yLxjLAYx0a BsKQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id e5-v6si338138edi.4.2018.07.22.23.55.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Jul 2018 23:55:47 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w6N6tlAT011338 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 23 Jul 2018 08:55:47 +0200 Received: from [139.22.37.206] ([139.22.37.206]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id w6N6tkar004770; Mon, 23 Jul 2018 08:55:47 +0200 Subject: Re: [PATCH v3 0/7] Isar cross-compilation support From: Jan Kiszka To: Alexander Smirnov , isar-users@googlegroups.com References: <20180717131811.14239-1-asmirnov@ilbers.de> <5c45490f-9dce-b43a-14b3-8347931c40ef@siemens.com> <507beff8-3503-22a9-c3f6-0a01f3f7a132@ilbers.de> <1ed1ad84-acaf-1aa9-0ac7-f2f1353670ab@siemens.com> <164aa001af8.27ac.034a6b0541ed39b7fb4e17f4ac219eaa@ilbers.de> <09de613b-ba4c-21fb-d675-421c27b9bab6@ilbers.de> <610e26c8-4af8-6a96-7ed5-76470fb4298e@siemens.com> <2ce080a3-ab36-6a00-c8cb-80ff2d39b7f3@siemens.com> <877fdc7a-c6c7-5192-0113-ce4b9a0f5b68@ilbers.de> <9670ec25-f1af-daac-53c3-f92c0db3f573@ilbers.de> <0d9010d4-df48-c87c-8b36-2365229d7566@siemens.com> Message-ID: <41d9e7c9-38c5-0d9b-5e7c-36c03a2ec4d0@siemens.com> Date: Mon, 23 Jul 2018 08:55:46 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <0d9010d4-df48-c87c-8b36-2365229d7566@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: ssBY68uYuerB On 2018-07-22 23:54, [ext] Jan Kiszka wrote: > Hi Alex, > > On 2018-07-22 22:32, Alexander Smirnov wrote: >> Hi Jan, >> >> On 07/22/2018 11:15 PM, Alexander Smirnov wrote: >>> >>> >>> On 07/20/2018 08:56 AM, Jan Kiszka wrote: >>>> Hi Alex, >>>> >>>> On 2018-07-19 22:59, Alexander Smirnov wrote: >>>>> Hi Jan, >>>>> >>>>> [...] >>>>> >>>>>>> Just an observation, you use here buster but I didn't test it. >>>>>> >>>>>> Yes, but only for the pre-built u-boot package, and only for the >>>>>> Orange >>>>>> Pi. See conf/multiconfig/preferences.orangepi-zero.conf. >>>>> >>>>> I've found several issue with v3 regarding kernel and modules >>>>> cross-compilation. I've fixed them and pushed asmirnov/devel branch. >>>>> >>>>> Now I'm able to cross-build orangepi kernel and example-module for >>>>> it, huh! :-) >>>> >>>> That's good news, and I can confirm that at least the linux-headers >>>> packages looks good now. It's also clear now that there can be no >>>> mixed-mode when building kernel modules because this package with its >>>> host tools is generated for the build host, not the target arch. >>>> >>>> However, I'm still stuck on the Python dependency problems. I bet you >>>> can also reproduce them by declaring the hello package to >>>> build-depend on "python". Same for "python-pip". >>>> >> >> I've found an interesting notes here: >> >> https://wiki.debian.org/DebianBootstrap/TODO#Remove_blockers_for_:any_and_:native_introduction >> >> >> adding native qualifier for python solves the issue for me (i.e. >> python:native). > > Yes, already wanted to report (but got distracted by Jailhouse bugs) > that I found the same hint in > > https://groups.google.com/forum/#!topic/linux.debian.devel.mentors/OuuorAmGgWc > > Adding :native to python solved the build issue for non-root-initramfs > in jailhouse-image. But I have harder nuts in that repo. :) > > The jailhouse package has build dependencies on python-mako, a package > mentioned above as cross-incompatible, and also python-pip. Those can be > installed by adding :native as well, but dpgk-buildpackage will then > fail on validating the build dependencies. That can be skipped, though: > > diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh > index 40ba410..aba2042 100644 > --- a/meta/recipes-devtools/buildchroot/files/build.sh > +++ b/meta/recipes-devtools/buildchroot/files/build.sh > @@ -61,4 +61,4 @@ for i in configure aclocal.m4 Makefile.am Makefile.in; do > done > > # Build the package > -dpkg-buildpackage -a$target_arch > +dpkg-buildpackage -a$target_arch --no-check-builddeps > > With that change and by adding arm64 support, I was now able to build > *all* jailhouse-image targets cross! > >> >> Do you think current status contains enough functionality for the first >> implementation, so I could format clean patches and add the documentation? > > Yes, definitely, with that workaround and arm64 support, please. Maybe > you have an idea how to limit the --no-check-builddeps to cross-builds. > > I noticed one further minor thing: wic images seem to enforce generating > buildchroot-target. I suppose wic will be fine with buildchroot-host as > well. Would be nice to avoid that redundant bootstrap if possible. > FWIW, I've pushed all required changes to jailhouse-images to its next branch. You just need to adjust the kas file to point to a compatible isar revision (your branch + arm64 + my workaround) and add diff --git a/kas.yml b/kas.yml index 64e80c5..0158ae5 100644 --- a/kas.yml +++ b/kas.yml @@ -33,3 +33,5 @@ bblayers_conf_header: local_conf_header: standard: | CONF_VERSION = "1" + cross: | + ISAR_CROSS_COMPILE = "1" Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux