From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: Re: Heap space when building SBCL packages Date: Mon, 23 Mar 2020 18:17:58 +0100 Message-ID: References: <87sghz86cj.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:48062) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jGQiA-0002b0-Ko for help-guix@gnu.org; Mon, 23 Mar 2020 13:18:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jGQi8-0000F2-Vj for help-guix@gnu.org; Mon, 23 Mar 2020 13:18:02 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:55103) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jGQi8-0000Er-O7 for help-guix@gnu.org; Mon, 23 Mar 2020 13:18:00 -0400 In-Reply-To: <87sghz86cj.fsf@ambrevar.xyz> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org Sender: "Help-Guix" To: Pierre Neidhardt , help-guix@gnu.org Hi Pierre, >> 2. Building binaries with SBCL takes more heap space than merely >> loading a system from source via ASDF. > > I think probably not. However there are different ASDF operation. In the > Guix build system we use "program-op" which does not behave like the > default operation when loading a package. This could be a factor here. Worth testing, if only to have a non-Guix way to illustrate the issue for reporting upstream if necessary. Is there a way to get the exact ASD file plus command line that is used by the build system? >> 3. Guix' build systems does something that either limits heap space >> or causes SBCL to require more of it. >> >> Does anyone have an idea on how to proceed to fix the problem? > > Can you reproduce with SBCL 2.0 or SBCL 1.5? Building sbcl-numcl works fine with 1.5 and 2.0. It's only with 2.0.2 that there is this heap issue. > Maybe report this issue to the SBCL issue tracker, they will probably > know what's going on. If it's not a Guix issue, then yes, that's the way to proceed. Cheers, Konrad.