From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6482619450789986304 X-Received: by 10.28.229.139 with SMTP id c133mr259565wmh.13.1509462028688; Tue, 31 Oct 2017 08:00:28 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.163.22 with SMTP id c22ls4104038wrb.0.gmail; Tue, 31 Oct 2017 08:00:28 -0700 (PDT) X-Google-Smtp-Source: ABhQp+RwKE5GYMUiIUfa7lUeLUXK15ucdI0eM7F7RUby60jqDuQsyJzgWzO1KMCDZ5a7HFrDtpTH X-Received: by 10.28.128.140 with SMTP id b134mr265897wmd.3.1509462028224; Tue, 31 Oct 2017 08:00:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1509462028; cv=none; d=google.com; s=arc-20160816; b=KSwRST2lk9eOIG6kA88s+hbT13MgcZLaERPNqtDxjF7Q/aFZ21EfQOjkzaLiDLBBQt bmyLkj0rtL6m/xSX3DNtaaft1ml6//2hN2a3HTnr4WC0tEdMbFseg//jujqJ6F/WnK7G CmwJA5DunwHwTnF0/g0mZIHXEVGdwy0uyyUUsZwCMWazcBbS0pi7bgFuEf8PMC+KW4Ja LuB8mNH3T7Vr1ZSgq4V6nKw8bo3LxNwoNqxODAbd5ieyVeZ/Kq7WfudKRaSsyQKc5t8z gWUKAPnM9Z65rw1Oz1C+Fo1Riv3/YFtd3uGd7plHkjsk/uz4nMosADWbc2j/dYFlppFw hoFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date :arc-authentication-results; bh=c144co9WWyBjbIFjQBkKeTwlUt71rdsWL6ymBm5+pes=; b=BxPC3dkqvmMHrh69IsapOAnxxIrqoMJ82kz/yPlJjr1lS0ebFBkXAcWmkMsqjsNeJO 94SavvbwlAvMybOvyszMbu/TzgCUt7R4YDmvcAYY7zkzgnQXT5vkttkcNfd/ET4skM69 9v46x83L12bAbrInRSWha4eLCwO6tB7Kg9j2NljYRWnEJ44rfwb8dhTI/e3Eef0rtt81 dcd0H5YVlKyijZE65jYRayi3+6Zj2lcmC7tsHk9d1syf9wPiwSLOsxc5tTFMCD6H4g6M CrD8rxgKj49l/+vm9GyxKvS8DyqMBX29FYjiB1TugYaGgrJw8VVCzfziOyhlJ3c1buU8 1lhQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id k11si128899wmi.1.2017.10.31.08.00.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Oct 2017 08:00:28 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.radix50.net (ipservice-092-219-221-042.092.219.pools.vodafone-ip.de [92.219.221.42]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id v9VF0P4n020543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 31 Oct 2017 16:00:27 +0100 Received: from yssyq.radix50.net (localhost [127.0.0.1]) by yssyq.radix50.net (8.14.4/8.14.4/Debian-8) with ESMTP id v9VF0Knp011173 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 31 Oct 2017 16:00:20 +0100 Received: (from ibr@localhost) by yssyq.radix50.net (8.14.4/8.14.4/Submit) id v9VF0KWx011172 for isar-users@googlegroups.com; Tue, 31 Oct 2017 16:00:20 +0100 Date: Tue, 31 Oct 2017 16:00:20 +0100 From: Baurzhan Ismagulov To: isar-users Subject: Re: Cross-building and debugging Message-ID: <20171031150020.GC5385@yssyq.radix50.net> Mail-Followup-To: isar-users References: <0b55db7d-e602-4f4b-b6d5-bc1c0a0e18e8@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0b55db7d-e602-4f4b-b6d5-bc1c0a0e18e8@googlegroups.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-TUID: 8tRpmkJplK0O Hello Andrea, On Mon, Oct 30, 2017 at 01:34:19AM -0700, andrea.marson.dave@gmail.com wrote: > IIUC, when using Isar it is implicitly assumed that the user applications > are natively built on the target. The current implementation builds user applications natively in buildchroot using qemu on the host. This was a customer requirement to avoid having to tweak Debian packages which one may happen to want to rebuild and which don't support cross-building. That said, Isar's predecessor is based on cross-building, which is state of the art in Emdebian and has its advantages in certain use cases. > If, for any reason, this is not possibile, one has to cross-build the > applications. > Which approach do you recommend to set up the cross-build environment, in > order to make it work smoothly with Isar? Basically, it worked like this: 1. Install cross-toolchain (e.g., gcc-arm-linux-gnueabihf) into buildchroot. 2. Modify the package's debian/rules for cross-building (e.g., pass the right --host=arm-linux-gnueabihf to ./configure). 3. Cross-build (e.g., call dpkg-buildpackage with --arch=arm or similar). I don't remember the details, so the quotations above are not literal. There is a branch https://github.com/ilbers/isar/tree/lenormf/develop-l20170602-dpkg-cross which should support cross-building. We plan to refine it and propose for integration into master. Till then, you might use the current qemu approach or look at the branch above (will probably require some hacking). If you can share your use case, maybe we could suggest something. E.g., GLIB doesn't cross-compile out of the box due to configure failing to run test programs for the target; supplying the test results to configure pre-canned in a file makes it happy. With kind regards, Baurzhan.