From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44536) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e7m2f-0005XV-Kw for guix-patches@gnu.org; Thu, 26 Oct 2017 13:34:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e7m2c-0005ay-FA for guix-patches@gnu.org; Thu, 26 Oct 2017 13:34:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:54941) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e7m2c-0005ao-C3 for guix-patches@gnu.org; Thu, 26 Oct 2017 13:34:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e7m2c-0002DL-2o for guix-patches@gnu.org; Thu, 26 Oct 2017 13:34:02 -0400 Subject: [bug#26339] closing bootloader serie. Resent-Message-ID: References: <20170402134916.2871-1-m.othacehe@gmail.com> <87d15rdtsb.fsf@gmail.com> <87d15rm5dl.fsf@gnu.org> <87zi8e1by3.fsf@gmail.com> <87she5hlwi.fsf@gnu.org> From: Mathieu Othacehe In-reply-to: <87she5hlwi.fsf@gnu.org> Date: Thu, 26 Oct 2017 19:33:36 +0200 Message-ID: <87d159yftb.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 26339@debbugs.gnu.org > That said, I experimented with cross-compiled GuixSD (that is, ‘guix > system build --target=foo-linux-gnu’), and I think that’s promising, > with the caveat that you have to restrict your package set to those that > can actually be cross-compiled. Should we try to get it off the ground? That would be really interesting. But to build an arm GuixSD installer for example, it would require that are all the packages needed to set-up the rootfs of the installer are cross-compilable, right ? Also, something I don't understand here. This does not work (without armhf offloading machine): --8<---------------cut here---------------start------------->8--- ./pre-inst-env guix system disk-image --file-system-type=iso9660 --system=armhf-linux gnu/system/boards/beaglebone-black.scm guix system: error: build failed: a `armhf-linux' is required to build `/gnu/store/pswlzi1bwdzalfidbzf5w96fbdiv3dc1-linux-libre-arm-omap2plus-4.13.8.drv', but I am a `x86_64-linux' --8<---------------cut here---------------end--------------->8--- but this works : --8<---------------cut here---------------start------------->8--- ./pre-inst-env guix build --target=arm-linux-gnueabihf linux-libre-arm-omap2plus /gnu/store/53lcpmpkbba661h3lrnxms1dfz750gw5-linux-libre-arm-omap2plus-4.13.8 --8<---------------cut here---------------end--------------->8--- What's the difference between --system=armhf-linux and --target=arm-linux-gnueabihf ? Why guix system do not use the already cross-compiled kernel and asks me to build it on an armhf machine ? Thanks, Mathieu