From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6931461770728964096 X-Received: by 2002:a5d:4908:: with SMTP id x8mr2076136wrq.164.1613987518606; Mon, 22 Feb 2021 01:51:58 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:60c2:: with SMTP id u185ls7225074wmb.2.gmail; Mon, 22 Feb 2021 01:51:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJw6lwq3Rif78/f1CakcUb+fGjEEzipuANQhdD79qKXrWqFpEMEfSnaALp5RSxLmUcqboWyD X-Received: by 2002:a05:600c:190f:: with SMTP id j15mr19513644wmq.174.1613987517761; Mon, 22 Feb 2021 01:51:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613987517; cv=none; d=google.com; s=arc-20160816; b=lsKDMBYusE2agdrOneFRWilJvmqfFk8mduDqPRxr6wumWc2P76PC3atjLHlTLOPNL7 QyV+Bk4UvMjz9wQwPljk57s+vGJqng+VChZqr+fBGAzGXPrDJkfdpFS64yZCuzaOVWTO 2TpL1beyH0wFqFaRDYoH6WtvGuqNzqYC5ZlWery0b0Qq0QuX7iZfBoMNnoUAJuxm4SDd 5whIlvV/AotYzera1VAkwEBYM/FrBH4KXItwdNyogvNYUtROs5Z07YEXSUCIJY17Yu4t NkJN6d76lBphW5R6VW/jwNgZSv5bjrttiB6Hwasm74JE7qcq1qltPpUcDhX97/mB3olD ZPUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-language:content-transfer-encoding:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=vXzJjC27myhbNgKeQ6PBfRfvHN+H7kLKIrnTesMKe1k=; b=tbsyNblE+kiXuzQaOb16F5eRhbxz6epkTmOeGv1u2ALX3e1QANsy3XigfPCSbE6IPM fI5XJMqsZGIwM8xdoK0J7GZggUJuNKVapnixf75w/1q1Bq9mCXgh2No8qyTOjRNLf36+ Rz9r5aBDFvQ4vE6KbD/SccdDxGqLsAowo7rr/2G052jyxutSpjMkAtjoONTXISJt6fhS obolClROnvFdw4z5Oy+r8e5QuqvQXbrBTpZREBK3FAVgYIxtyoQdeFQIBlCqQ2bA3HMg G95NfcYlMgaep8t/c3lQjIyJovD0SIojT5J6MmkPkTnM2+xjr825id5iiW0Fzsfm67lZ +1gA== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id m3si1052044wme.0.2021.02.22.01.51.57 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Feb 2021 01:51:57 -0800 (PST) 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id 11M9pvBl029156 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 22 Feb 2021 10:51:57 +0100 Received: from [167.87.76.32] ([167.87.76.32]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 11M9fuS3016021; Mon, 22 Feb 2021 10:41:57 +0100 Subject: Re: Relocation of SDK To: Daniel Machon , "isar-users@googlegroups.com" References: From: Jan Kiszka Message-ID: Date: Mon, 22 Feb 2021 10:41:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-TUID: M5L+y1Gip/7N On 20.02.21 22:31, Daniel Machon wrote: > > Hi, > >   > > I have been working with the SDK lately, and came across a rather > unfortunate side-effect of the relocation of the SDK. > >   > > When the SDK is relocated, the interpreter and the RPATH of **ALL** > the binaries are changed to that of the host system. This means that a > developer can not longer chroot into the SDK. > Right - but then don't relocate in the first place. >   > > I would argue, that a common development workflow would be to use the > cross-toolchain provided by the SDK, and then chroot into the SDK to > install dependencies (we have the possibility of installing multiarch > packages). This is currently not possible, because the interpreter and > the RPATH is change for all the binaries of the SDK. > You can add missing packages upfront, see SDK_* variables. This is superior anyway because an SDK is a snapshot that may have a hard time still finding fitting dependencies that weren't included at build time. >   > > Why not only change the interpreter and RPATH of the cross-toolchain > binaries? These are the binaries that are meant to be run on the host > anyway. > > If you need to change the RPATH of any libraries (I came across this > need when trying to make gdb available to the host), you can make > RPATH relative using $ORIGIN. > As Baurzhan commented, this is not that easy. I think we have two clearly different use cases than can be derived from the same SDK tarball - but not run at the same time. Also note that there will be a better alternative to privileged chroots: SDK container images. See patches on the list. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux