From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6594490675806339072 X-Received: by 2002:a2e:7819:: with SMTP id t25-v6mr10878ljc.35.1535399508191; Mon, 27 Aug 2018 12:51:48 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:998d:: with SMTP id w13-v6ls10507lji.14.gmail; Mon, 27 Aug 2018 12:51:47 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZUvUauLf99z+sBJP9KHrYtMUFUOJojM3D+sdejZhQS2Q5TDhaV+eAFcQo57XAEjoZpS55u X-Received: by 2002:a2e:380e:: with SMTP id f14-v6mr19057lja.14.1535399507594; Mon, 27 Aug 2018 12:51:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535399507; cv=none; d=google.com; s=arc-20160816; b=kjZKb/pvjBGxwsoNnDpmisjuGaH2mAj9N2Nd9fE5re+lDBJ3QSKx/CMtev6zPyFCMG /xsaGhwVilQ9O7ExcENBP0NsNu6S55Nulm1tvKLdUsUDidRjb27NH4A2hLvtp1DGK0TO Tbnu3kxjQs7ihqoRh7HfsEWV1Ig52rImkzsmNvQyLFw26kEznYIva9ChPGYr8UdiFFU/ J2fwgO2w6qQr2LTY5TgDiAavEzQdc+BT2NrmC38X7D7RHn1Y5sgVlKGBsyyYVYS46g+g pCrg35k+i3fZTTE70zdgGXf270R7Jgh81Kdvj8UThC7he04GL1HWxu9APORtCNsv5jfY 7mDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:mime-version:user-agent :date:message-id:subject:from:to:arc-authentication-results; bh=OD4FN0jKahsSYI1aLcnITsBvQs0BPDQo5RqS0U1o0sw=; b=uPlD/sd9P6uUwedf6Q5utCYg+Pp6EUY9Snq3tfbRsMCohAgmj6Ns+LqNpTrk0QO7PB Bx0Mx2WaIf0NWSPuevjZl+7P2v5QNotv3quhp+TcCpCGKwpBJzzOyAHmdXYJfcFXz16R 8WgQFbwL4WwaIo8Hrcr54gyHZbdlOdxhpBoK+EfHybBHoQmNCGMz6doQWZd66a2lKUF8 cE5cGu/nVddu1LkL0rIEeQVfqUmjF8hT8EEF6yDQDMFvDj9rlx4zJtG+5NtOF8enpse8 AdfghzNTWZ5iYuA7xKgMFaH4f/7vxkNyTkqW3mpv1nDd7ikV27ChCoEuWxCyvmC3sY6C uiKg== 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 v16-v6si4012ljg.3.2018.08.27.12.51.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Aug 2018 12:51: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 w7RJpkKm023171 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 27 Aug 2018 21:51:46 +0200 Received: from [167.87.34.56] ([167.87.34.56]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id w7RJpjBp029425; Mon, 27 Aug 2018 21:51:45 +0200 To: isar-users , Alexander Smirnov , Maksim Osipov From: Jan Kiszka Subject: crossbuild broken with host-distro != target-distro Message-ID: <7074054d-bb57-dc87-5bb4-f74eca265c51@siemens.com> Date: Mon, 27 Aug 2018 21:51: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 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: oM8XgpNARb5s 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 -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux