GNU bug report logs - #67535
ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux

Previous Next

Package: guix;

Reported by: Leo Famulari <leo <at> famulari.name>

Date: Wed, 29 Nov 2023 20:56:02 UTC

Severity: normal

Done: Leo Famulari <leo <at> famulari.name>

Bug is archived. No further changes may be made.

Full log


Message #59 received at 67535 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: guix-devel <at> gnu.org, 67535 <at> debbugs.gnu.org, Leo Famulari <leo <at> famulari.name>
Subject: Re: Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org
 'Cannot allocate memory' while building for i686-linux]
Date: Sun, 10 Nov 2024 20:56:33 +0900
Hi,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Efraim Flashner <efraim <at> flashner.co.il> skribis:
>
>> On Fri, Jul 26, 2024 at 02:51:49PM -0400, Leo Famulari wrote:
>>> For a long time we've not been able to build linux-libre on i686-linux
>>> because the source unpacking process runs out of memory.
>>
>> I believe if we limit the unpacking process to not more than 8 cores we
>> can avoid that problem.
>
> Also, this is very much a defect of xz; on ‘core-updates’,
> ‘patch-and-repack’ uses zstd, which is much less memory-hungry and more
> predictable.

I was about to write this; thanks for be6g faster :-).  I believe the
unpacking should now be fine even for i686, Leo?

-- 
Thanks,
Maxim




This bug report was last modified 191 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.