From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 8Fz1Eq+oLmAjGQAA0tVLHw (envelope-from ) for ; Thu, 18 Feb 2021 17:49:35 +0000 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id YCrGDq+oLmCbSAAA1q6Kng (envelope-from ) for ; Thu, 18 Feb 2021 17:49:35 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id E21EF31C0E for ; Thu, 18 Feb 2021 18:49:34 +0100 (CET) Received: from localhost ([::1]:57100 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCnQj-00070y-Vf for larch@yhetil.org; Thu, 18 Feb 2021 12:49:33 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:33426) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCnDE-00043M-Uu for guix-devel@gnu.org; Thu, 18 Feb 2021 12:35:38 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:46922) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCnDE-0004gu-C2; Thu, 18 Feb 2021 12:35:36 -0500 Received: from [2a01:e0a:1d:7270:af76:b9b:ca24:c465] (port=46822 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lCnDB-0006eq-0F; Thu, 18 Feb 2021 12:35:36 -0500 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Christopher Baines Subject: Re: Getting the Guix Build Coordinator agent working on the Hurd References: <87tuqekheb.fsf@cbaines.net> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 30 =?utf-8?Q?Pluvi=C3=B4se?= an 229 de la =?utf-8?Q?R=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu Date: Thu, 18 Feb 2021 18:35:31 +0100 In-Reply-To: <87tuqekheb.fsf@cbaines.net> (Christopher Baines's message of "Sun, 14 Feb 2021 11:39:24 +0000") Message-ID: <87v9app9cs.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -1.37 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: E21EF31C0E X-Spam-Score: -1.37 X-Migadu-Scanner: scn1.migadu.com X-TUID: sK942/mgyMNF Hi! Christopher Baines skribis: > Then I faced two problems with the guix-build-coordinator > package. Firstly, wrap-program picks bash for Linux for the wrapper > script, which isn't very useful. I hacked around this by setting the > PATH such that it picked bash for the Hurd. In terms of properly fixing > this, I guess that needs to somehow be able to find the right bash, I'm > not sure how though? Looks like a bug in =E2=80=98wrap-program=E2=80=99 that we should fix in = =E2=80=98core-updates=E2=80=99. =E2=80=98wrap-program=E2=80=99 uses (which "bash"), which is wrong in a cross-compilation context. We should at least add a #:bash parameter to =E2=80=98wrap-program=E2=80=99= , but then all callers will have to pass it. I=E2=80=99m not sure how to let it do the right thing by default. > The second issue is that I'm not sure capturing the build time > GUILE_LOAD_COMPILED_PATH doesn't seem to work, at least file says that > the .go files this contains are built for a 64-bit architecture. I > worked around this by constructing the GUILE_LOAD_COMPILED_PATH from the > inputs I knew should be on it. Maybe it should always have been done > this way, any ideas? Instead of capturing the build-time =E2=80=98GUILE_LOAD_COMPILED_PATH=E2=80= =99, which doesn=E2=80=99t contain the target .go files, you should explicitly list the inputs as is done in the =E2=80=98guix=E2=80=99 package for example. That= =E2=80=99ll ensure the binary refers to the cross-compiled .go files. > There's also one problem probably within the Guix Build Coordinator > itself, after doing a few builds, it will just stop. I've only seen this > behaviour on the Hurd, but I'm unsure how to debug it, any suggestions? > My only idea is add more logging. No idea, but I guess that could just be a crash. Can you still log in afterwards? BTW, note that builds on GNU/Hurd are currently not isolated, and thus it=E2=80=99s the wild west in terms of reproducibility: https://issues.guix.gnu.org/43857 There are open questions as to what to include in the build environment: https://guix.gnu.org/en/blog/2020/childhurds-and-substitutes/ Ludo=E2=80=99.