From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, 67535@debbugs.gnu.org,
Leo Famulari <leo@famulari.name>
Subject: bug#67535: 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 [thread overview]
Message-ID: <87h68fwbda.fsf@gmail.com> (raw)
In-Reply-To: <87h6bpdeia.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 12 Aug 2024 16:03:57 +0200")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Efraim Flashner <efraim@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
WARNING: multiple messages have this Message-ID (diff)
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Leo Famulari <leo@famulari.name>,
67535@debbugs.gnu.org, guix-devel@gnu.org
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 [thread overview]
Message-ID: <87h68fwbda.fsf@gmail.com> (raw)
Message-ID: <20241110115633.isQyJ0QClPBTQx2Pj_KReEqq0ujrdOSScrPEdy3vY9g@z> (raw)
In-Reply-To: <87h6bpdeia.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 12 Aug 2024 16:03:57 +0200")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Efraim Flashner <efraim@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
next prev parent reply other threads:[~2024-11-10 12:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZWelMw84qtyRxxS6@jasmine.lan>
[not found] ` <ZXBoKfOxrITAuOoF@3900XT>
2024-07-26 18:51 ` Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux] Leo Famulari
2024-07-26 20:17 ` Kaelyn
2024-07-28 21:49 ` Efraim Flashner
2024-07-29 12:33 ` Ricardo Wurmus
2024-07-29 15:00 ` Richard Sent
2024-07-30 0:01 ` Leo Famulari
2024-07-30 1:21 ` Richard Sent
2024-07-30 14:39 ` Leo Famulari
2024-08-01 23:51 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-07-30 15:18 ` Efraim Flashner
2024-11-10 12:32 ` janneke
2024-07-30 21:02 ` bug#67535: " André Batista
2024-08-01 20:12 ` Leo Famulari
2024-08-02 8:36 ` Ricardo Wurmus
2024-08-02 19:34 ` bug#67535: " André Batista
2024-09-05 9:42 ` Ricardo Wurmus
2024-09-05 23:52 ` André Batista
2024-08-12 14:03 ` Ludovic Courtès
2024-11-10 11:56 ` Maxim Cournoyer [this message]
2024-11-10 11:56 ` Maxim Cournoyer
2024-11-11 4:51 ` Leo Famulari
2024-11-12 12:59 ` Maxim Cournoyer
2024-11-12 16:13 ` Denis 'GNUtoo' Carikli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h68fwbda.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=67535@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).