From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6594490675806339072 X-Received: by 2002:a1c:9652:: with SMTP id y79-v6mr1652937wmd.29.1536136727261; Wed, 05 Sep 2018 01:38:47 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:8265:: with SMTP id 92-v6ls378109wrb.2.gmail; Wed, 05 Sep 2018 01:38:46 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYQkylmo9rxYWKGWgVcJXFxOthqGQYeutMPWIWuL6F+BhLZj/r9RGIQHX6Xl7MnXwMAE3Ko X-Received: by 2002:a5d:55cd:: with SMTP id i13-v6mr3317771wrw.2.1536136726744; Wed, 05 Sep 2018 01:38:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536136726; cv=none; d=google.com; s=arc-20160816; b=CdDkGxFVFkjFzhBJwy63lnKDhSTxv3B6NbCrbIMbWTjZP/m2MuXiX9ElcXcQ3HE1uB 6omUeBeEWB36lV9EKfMk/tTh8j1Utg7yb51hvfTzH06vXkXwXybuBbh5KuWwChn2VDM2 roT2iXKB17afa8R2kKGbBbmPsn/sSco7T/05qS/xTYESsndU++vrzP2AsT+vMFV45vqI ptdDDXNuwrj4F28AD5jjRqTLnDb8O4uNp+rgyYs1fPT80yS4Ly+TpJE08ZXUHipzZuCC gki4luILBKMhQ+ELjdtsPZ97yoKg+CiDHxQLal4YRIlvH7Iyv7lzqB269mdUJiiwWbnY clgQ== 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:from:references:cc:to:subject; bh=x92hTEJsKb2BglwJXD/sBx2Df5b0NFwTOmdjtIDVwu0=; b=c1TD2pj+56k4MSBUl4maoaJN9oeokLGslmIzASqhuZ+nyuWkFJYX3q1S/QziNRGjUZ RCQKLj1h6nTdMxjGEyXCJdOTTsO0K8KvkXRwF84ruBJyTGThyuIhsHTHPH2OUvim9Rwv XNKZCvKVFbtquv/A30um+yi3BuZ5bXzZV5Khmk00M0Jk+iib5/8XWvRCyviwhfRaHpXl B7NWdNTO/bQIc8VTUSwPryDRJ+V8mTYmrKfKD27B0zM4P0nxdLTmwDFZKH9BIkvES8nW RtjZlDpt7IGUjaXOHB4QdqbDxocz0wKEC1ZJyoXHISk2OCbDgRAGa5PhCB4b5Bn+VVKp Ha1A== 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 e18-v6si57166wrp.1.2018.09.05.01.38.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Sep 2018 01:38:46 -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 w858cjbW030625 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 5 Sep 2018 10:38:46 +0200 Received: from [167.87.2.38] ([167.87.2.38]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id w858cjd8013670; Wed, 5 Sep 2018 10:38:45 +0200 Subject: Re: crossbuild broken with host-distro != target-distro To: "Maxim Yu. Osipov" , Alexander Smirnov Cc: isar-users References: <7074054d-bb57-dc87-5bb4-f74eca265c51@siemens.com> <1f9a5d5c-ffcf-1a3f-1edf-d60bf653e651@siemens.com> From: Jan Kiszka Message-ID: <672b9026-df74-b51c-62e5-5e15898cba2c@siemens.com> Date: Wed, 5 Sep 2018 10:38:45 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: Qmv9j5HQuh7G On 2018-09-05 10:31, Maxim Yu. Osipov wrote: > Hi Jan, > > > On 08/30/2018 11:24 AM, Jan Kiszka wrote: >> On 2018-08-27 21:51, [ext] Jan Kiszka wrote: >>> Hi folks, >>> >>> I ran into a remaining glitch for the crossbuild support: When the >>> target distro name differs from the host distro, buildchroot-host fails. >>> >>> That initially looked like it would be easy to fix and even made sense >>> for a while: >>> >>> diff --git a/meta/recipes-devtools/buildchroot/buildchroot-host.bb >>> b/meta/recipes-devtools/buildchroot/buildchroot-host.bb >>> index daf92a2..01d426d 100644 >>> --- a/meta/recipes-devtools/buildchroot/buildchroot-host.bb >>> +++ b/meta/recipes-devtools/buildchroot/buildchroot-host.bb >>> @@ -30,5 +30,5 @@ BUILDCHROOT_PREINSTALL_append_arm64 += >>> "binutils-aarch64-linux-gnu \ >>>                                           crossbuild-essential-arm64" >>> -PARAMS = "--host-arch" >>> +PARAMS = "--host-arch --host-distro" >>>   do_build[depends] = "isar-apt:do_cache_config >>> isar-bootstrap-host:do_bootstrap" >>> >>> >>> However, that only broke setup_root_file_system differently because it >>> now tried to mount the non-existing host isar-apt repo. Workaround hack: >>> >>> diff --git a/meta/classes/isar-bootstrap-helper.bbclass >>> b/meta/classes/isar-bootstrap-helper.bbclass >>> index d45cdd7..4ad552f 100644 >>> --- a/meta/classes/isar-bootstrap-helper.bbclass >>> +++ b/meta/classes/isar-bootstrap-helper.bbclass >>> @@ -93,9 +93,9 @@ setup_root_file_system() { >>>           sudo tee "$ROOTFSDIR/etc/apt/preferences.d/isar" >/dev/null >>>       if [ ${COPYISARAPT} ]; then >>> -        sudo cp -Trpfx ${DEPLOY_DIR_APT}/${ROOTFS_DISTRO} >>> $ROOTFSDIR/isar-apt >>> +        sudo cp -Trpfx ${DEPLOY_DIR_APT}/${DISTRO} $ROOTFSDIR/isar-apt >>>       else >>> -        sudo mount --bind ${DEPLOY_DIR_APT}/${ROOTFS_DISTRO} >>> $ROOTFSDIR/isar-apt >>> +        sudo mount --bind ${DEPLOY_DIR_APT}/${DISTRO} >>> $ROOTFSDIR/isar-apt >>>       fi >>>       sudo mount -t devtmpfs -o mode=0755,nosuid devtmpfs $ROOTFSDIR/dev >>>       sudo mount -t proc none $ROOTFSDIR/proc >>> >>> >>> That will likely break sdkchroot, the only recipe that depends on >>> isar-apt-host, so far the only caller of setup_root_file_system that >>> passed --host-distro. But I'm not getting yet why the SDK has some own >>> isar-apt repo and no one else. Can you clarify and maybe even explain >>> how to fix the issue best? > > The initial idea is that sdk may be distributed to other hosts - > so we need to copy local isar-apt to sdk chroot. > Actually copying of isar-apt here is redundant, as the same is done > later in do_populate_sdk to get all latest prebuilt packages for target > distro. Please explain again the different roles of isar-apt vs. isar-apt-host, why we need both. Then we need some wording about why that ROOTFS_DISTRO -> DISTRO is correct. We can't merge such changes without explanations. No one will understand the code and its history this way. Jan > > >>> Thanks, >>> Jan >>> >> >> Could you comment on this bug? It's a blocker here. > > I'm OK with your patch - it's reasonable. I've throughly tested it > together with my v2 sdk: Move deployment to populate_sdk. > > Just sent a v2 series. > > Kind regards, > Maxim. > -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux