From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6594490675806339072 X-Received: by 2002:adf:b713:: with SMTP id l19-v6mr821587wre.8.1535621048713; Thu, 30 Aug 2018 02:24:08 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:650b:: with SMTP id z11-v6ls225622wmb.10.canary-gmail; Thu, 30 Aug 2018 02:24:08 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbWZW9OyDAWsP8zE1+7TD3B1T9LrZUM8a4lBh0vvJ49e0mKSMGoFk4pbbUaJnW4S0bXnrF7 X-Received: by 2002:a1c:94:: with SMTP id 142-v6mr136055wma.12.1535621048188; Thu, 30 Aug 2018 02:24:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535621048; cv=none; d=google.com; s=arc-20160816; b=cxcCUltx8WoxSf28zu6snja2maISdHYiQTYcOGWpFESKoEqKK8eikczTPlodb77Q5A esE89h871GsG4TCYzho4fw8+EBbKvZiSfR1a49v+nIHuJcjlToGjibaHuF48YAJFLn/G H4iln9cTOAfUtnLdnqt1w8nbP1a2lLp0blDqS5JFQIMENoLVlumadu1JSI4pXYoQ9xl+ jjs2wcNf4BZY6Urgruj11mRlRSVAMAnT2Wrfd11YWwb7TUz61qyd3GKV4lhQRp5z15dI BXnRw31AV1uk0hvf4+h9lBkoxasgP+S0w4Zd1y3LWoKE49VM6R+sdslElCI5S4UPxgw+ zkgg== 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:cc:references:to:from:subject; bh=SP3wxEyyDecMQYLKA6JiVvJtXxLaHInHff50LWcYzUM=; b=BTms1JZOm6z1l8LmLN5GWxclYqoYJtcDMwmR9bu0oz9u2/QyvDyJLHFwtW7qXzkzyt ZCKl83R4MnkJVACXW2B0Za+EpjASYzhh3bFQR5Yqpfqz2+0Gxe3QVi/A2+DxKWuJKp29 /yAH2NX/MpRYkzIPaAIg09mmk0L+iFWIZxSMsry3VhXbxJ/diM7EoqpsAUb2dV/dHDA/ x5d1JNHxasxj18dRCfPvy4Nosi/ouBsC+zGac90wYk91JMfMiMrvufgedTae9xdF/Hrs F+nA7TMMZtxY7lhpiEc26h2duPNAaNydaiNbS1bM+qLf+jmAAWJP4NXlhpbHEPIgM4RH daQQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id 196-v6si73685wmx.1.2018.08.30.02.24.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Aug 2018 02:24:08 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id w7U9O7fc024598 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 30 Aug 2018 11:24:07 +0200 Received: from [167.87.0.101] ([167.87.0.101]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id w7U9O7Ht025691; Thu, 30 Aug 2018 11:24:07 +0200 Subject: Re: crossbuild broken with host-distro != target-distro From: Jan Kiszka To: Alexander Smirnov , Maksim Osipov References: <7074054d-bb57-dc87-5bb4-f74eca265c51@siemens.com> Cc: isar-users Message-ID: <1f9a5d5c-ffcf-1a3f-1edf-d60bf653e651@siemens.com> Date: Thu, 30 Aug 2018 11:24:06 +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: <7074054d-bb57-dc87-5bb4-f74eca265c51@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: hmUNRoS8w8u8 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? > > Thanks, > Jan > Could you comment on this bug? It's a blocker here. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux