From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 4IbGIuF/zF4ncAAA0tVLHw (envelope-from ) for ; Tue, 26 May 2020 02:33:05 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id cNy3HuF/zF5wbAAA1q6Kng (envelope-from ) for ; Tue, 26 May 2020 02:33:05 +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 631C09400AF for ; Tue, 26 May 2020 02:33:04 +0000 (UTC) Received: from localhost ([::1]:52920 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdPOo-0004Ba-TP for larch@yhetil.org; Mon, 25 May 2020 22:33:02 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40716) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdPOh-0004BG-0B for help-guix@gnu.org; Mon, 25 May 2020 22:32:55 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:47009) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdPOf-0007U5-4B for help-guix@gnu.org; Mon, 25 May 2020 22:32:54 -0400 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 208D35C0048; Mon, 25 May 2020 22:32:52 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 25 May 2020 22:32:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terracrypt.net; h=date:from:subject:to:cc:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm1; bh= Uz4M+orF8/wtN76P0bmoQa+YJH0nB+/PSW61b9SOKy0=; b=zuEZjT+DkZ+7GYuI c3EH7VMrhYGpsO6gH9AiCsNNDfX1xl+dfz/3qRFf4+CrBUOe8YSdYsFfZzwoHIuE kP/MbjoVb+Acyh6Efo0dDxbpDZlHFyEyeqnVOPqsmaXNJXS/ufBwAm/mugMRkgON CGz8VeWpGy+ERxDKpmGMkwwjCZOZ3AUNph50xtsOMmcAsYA+xcLwD1sHN13SwyJt w216A02M4Xm2MjviZyMpLjvBJDF4lBph3eD/N6qiEvLxV7P6D1lPFDf0X1oOdc4I 0piE9vrSiMo4MCOdjoL1tP4MHDaASGP9vZ+aq9YHrCiLWbMBduJCpZfMHnjFy/s3 6EYZzA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Uz4M+orF8/wtN76P0bmoQa+YJH0nB+/PSW61b9SOK y0=; b=nkFDOsZVVReQlSom6LorCpIscpAtmf4z0cy4o43vy4xeTLmOIIm1I9sS/ vq9SFP3f8GhOAa+NVIKT98+u/mmmdBA6XM4PnlRF9JBK9iH3xUTXJMVlPxBKybqr 54Gkh6fezBWEAvIFmm0nRj8Eh+EbP7+AsORSaHHv2zDWRuWQmKquFmlJoWYvsafo Reb+fUfpvMHO0vk68iJ8CnjQRizpHVDhgIKnHTaPy11LHnI1lvWhGcGMwAUT6mTM BJyLlKHxtifUXeKWIRc8qWvY4co54uqCCa9IhIFp587oil76RZfK9lh+ZYXbKjiO eLLG8AtR5WHW5kcqjTTNoUxTP9Jsg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddvuddgheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffuvffkjghfofggtgfgsehtqh ertdertddunecuhfhrohhmpeflohhnrghthhgrnhcuhfhrvgguvghrihgtkhhsohhnuceo jhhonhgrthhhrghnsehtvghrrhgrtghrhihpthdrnhgvtheqnecuggftrfgrthhtvghrnh epteeufffhueetieffteffkeefkeffgeegkedthefhleeikedvgeegheduteevhffgnecu ffhomhgrihhnpehgnhhurdhorhhgnecukfhppeeiledrvdehfedrvdegjedrleeinecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepjhhonhgrthhh rghnsehtvghrrhgrtghrhihpthdrnhgvth X-ME-Proxy: Received: from [10.4.42.127] (c-69-253-247-96.hsd1.pa.comcast.net [69.253.247.96]) by mail.messagingengine.com (Postfix) with ESMTPA id 61987328005A; Mon, 25 May 2020 22:32:51 -0400 (EDT) Date: Mon, 25 May 2020 22:32:50 -0400 From: Jonathan Frederickson Subject: Re: Geiser and Guix - how to avoid long compilation steps? To: divoplade Message-Id: <1590460370.6021.0@terracrypt.net> In-Reply-To: <273ca8429baf5d148376e9ceb08dff87fce935eb.camel@divoplade.fr> References: <1590447777.1469.0@terracrypt.net> <273ca8429baf5d148376e9ceb08dff87fce935eb.camel@divoplade.fr> X-Mailer: geary/3.34.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=66.111.4.27; envelope-from=jonathan@terracrypt.net; helo=out3-smtp.messagingengine.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/25 22:32:52 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: help-guix@gnu.org Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=terracrypt.net header.s=fm1 header.b=zuEZjT+D; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=nkFDOsZV; dmarc=none; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Spam-Score: -0.21 X-TUID: wHR//gd+A/LZ Ah! Thanks for the hint about the version of Guile. Turns out it was actually the other way around; I had built Guix with=20 Guile 3 but still had Guile 2.2 in my profile. This explains why an=20 ad-hoc environment with Guile worked just fine, but Guile in my normal=20 profile did not. (Looks like Guix gained support for Guile 3 prior to=20 version 1.1.0: https://guix.gnu.org/blog/2020/gnu-guix-1.1.0-released/) On Tue, May 26, 2020 at 2:05 am, divoplade wrote: > Hello, >=20 > I think that guix does not support guile 3 yet, so you should have > guile 2 bytecode for the guix modules. If geiser starts guile 3, then > guile 3 will recompile everything because the bytecode format changed > (and it could even compile native code). >=20 > Maybe it could work if you used guile 2.2 with geiser. >=20 > divoplade >=20 > Le lundi 25 mai 2020 =E0 19:02 -0400, Jonathan Frederickson a =E9crit : >> I've been using Geiser to hack on Guix lately, which is absolutely >> wonderful to use when it works. The trouble is, after I upgrade my >> system's Guix, Guile attempts to compile large portions of Guix when >> I >> attempt to switch to the module I'm working on in Geiser, e.g.: >>=20 >> M-x run-guile >> ,m (gnu services games) >>=20 >> This despite the fact that I'm working on a copy of Guix that I've >> already compiled with 'make' and that has the compiled copy >> alongside >> the source. The compilation step takes a *long* time on my hardware, >> which is fairly painful when I want to hack on Guix. >>=20 >> I do have my Guix checkout in geiser-guile-load-path in my emacs >> config >> as per >> https://guix.gnu.org/manual/en/html_node/The-Perfect-Setup.html: >>=20 >> (with-eval-after-load 'geiser-guile >> (add-to-list 'geiser-guile-load-path "~/sources/guix")) >>=20 >> My guess is that Guile is picking up my system's version of Guix >> before >> my local copy. I understand that I could start a version of Emacs in >> a >> pure ad-hoc environment (and Guile doesn't appear to start >> recompiling >> Guix when I do so), but the typical Emacs workflow is to have a >> long-running Emacs session and use that for everything; that's what >> I'm >> used to, and I'd like to continue to do so if possible. >>=20 >> Does anyone else experience this? What's the best way to use Geiser >> to >> hack on Guix when running Guix System? >>=20 >>=20 >>=20 >=20 =