unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Leo Famulari" <leo@famulari.name>,
	"Ludovic Courtès" <ludo@gnu.org>,
	67535-done@debbugs.gnu.org, guix-devel@gnu.org, neox@gnu.org,
	"Jason Self" <j@jxself.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: Tue, 12 Nov 2024 17:13:23 +0100	[thread overview]
Message-ID: <20241112171323.619c734b@primarylaptop.localdomain> (raw)
In-Reply-To: <87bjyk38w1.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]

Hi,

On Tue, 12 Nov 2024 21:59:42 +0900
Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> Great.  That said, I wouldn't be against stopping building i686
> packages on our build farm.  Nobody has shown much interested in
> fixing the broken ones or hunting down test failures... it seems
> better to focus our energy elsewhere and clear the view in my opinion
> (such as old bugs on our bug tracker that lingers on)
> 
> So I'd be of the opinion to:
> 
> 1) Stop building i686 packages
> 2) Otherwise preserve the architecture in Guix source so that someone
> can at least build from source and hack on it if they wish, e.g. to
> test cross-building packages.
In GNU Boot we chose to use i686-linux as the system we build packages
for as this way we support both i686 and x86_64 (some of the computers
we support are still i686).

Though for now we fixed the revision to Guix 1.4.0 so it means that we
don't find regressions affecting newer revisions.

I also personally also depend on i686 computers (ThinkPad X60) that I
don't use every day but that are important for me: they hold the
signature key of my gpg key and they are way easier to secure than
x86_64 machines against evil maid attacks (the machines were audited,
and don't allow DMA from external ports unlike all the x86_64 machines
supported by GNU Boot). But here too they are not updated regularly.

So does it means that we ultimately need to run our own builder for
i686 or are there other options (like setting up our own CI, going back
to i686 to test builds (I was running i686 to be able to find and fix
what didn't work before), etc), using latest Guix revisions to test more
often, etc?

All the use cases above only require very basic software to work: we
don't need full blown desktop systems (that would probably require to
bootstrap rust and I didn't really manage to find a way that would work
in Guix).

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-11-12 16:17 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         ` bug#67535: " Maxim Cournoyer
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 [this message]

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=20241112171323.619c734b@primarylaptop.localdomain \
    --to=gnutoo@cyberdimension.org \
    --cc=67535-done@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=j@jxself.org \
    --cc=leo@famulari.name \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=neox@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).