all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: "Efraim Flashner" <efraim@flashner.co.il>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>,
	guix-maintainers@gnu.org, Julien Lepiller <julien@lepiller.eu>,
	Marius Bakke <marius@gnu.org>
Subject: Re: Supported architectures
Date: Wed, 12 Oct 2022 13:40:21 -0700	[thread overview]
Message-ID: <875ygokc7e.fsf@contorta> (raw)
In-Reply-To: <Yz/FHD608HeU6iIM@3900XT>

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

On 2022-10-07, Efraim Flashner wrote:
> On Thu, Oct 06, 2022 at 04:50:22PM +0200, Ludovic Courtès wrote:

> Firstly, I'd like to mention that we, in general, have a minimum system
> requirement of 2GB of RAM, and IIRC there aren't a lot of armhf boards
> out there which have that much. We do have a difference between building
> natively and cross building / building with '--target'.
>
> I'd like to comment on armhf for a moment. My memory is a but rusty, but
> I'm pretty sure that in December of 2021 mesa was bumped from 21.2.x to
> 21.3.x, and at that time it stopped building on/for armhf. I noticed in
> May of 2022 (5 months later) and got the build working again. That we
> went 5 months without anyone saying anything in bug reports that mesa
> wasn't building shows that either everyone who is using it is using
> software that doesn't use mesa, or we really don't have any armhf-linux
> users. I'm not advocating dropping the architecture, but it does feel
> like we're already at a best-effort level with it. As far as the pieces
> needed for bootstrapping aarch64 software (go and probably others),
> those get built anyway as needed by aarch64, so there's no worry about
> losing support for those software bits.

FWIW, on Debian guix 1.3.0 is currently at risk due to armhf and
i386/i686-linux missings builds due to test suite failures. It has been
hard to keep up with Guix in Debian, especially supporting "obscure"
platforms...

Though I'm guessing there may be reluctance to drop support for
i686-linux... I much more frequently encounter test suite failures when
building it, at least on Debian. It is surely less well supported than
x86_64-linux.

But dropping armhf and i386 at the moment looks ... helpful from a
Debian packaging perspective... :/

I'll try to package a git snapshot of guix and see if that fares any
better and hopefully find and fix issues before the next guix release!

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2022-10-12 20:41 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07  9:49   ` Ludovic Courtès
2022-10-07 10:14     ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07  9:50   ` Ludovic Courtès
2022-10-07  9:53     ` Maxime Devos
2022-10-07  6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02   ` Ludovic Courtès
2022-10-07 14:24   ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08  9:55     ` pelzflorian (Florian Pelz)
2022-10-08 15:33     ` jbranso--- via Guix-patches via
2022-10-10 10:07       ` pelzflorian (Florian Pelz)
2022-10-14 15:12         ` Ludovic Courtès
2022-10-14 15:47           ` kiasoc5 via Guix-patches via
2022-10-15  9:47             ` pelzflorian (Florian Pelz)
2022-10-16 11:53               ` pelzflorian (Florian Pelz)
2022-10-14 17:09           ` pelzflorian (Florian Pelz)
2022-10-15 15:51             ` pelzflorian (Florian Pelz)
2022-10-17 16:35             ` Ludovic Courtès
2022-10-14 19:28           ` jbranso--- via Guix-patches via
2022-11-03 19:21           ` Ludovic Courtès
2022-11-16  0:22     ` pelzflorian (Florian Pelz)
2022-11-16 23:16       ` jbranso--- via Guix-patches via
2022-11-17 16:26         ` pelzflorian (Florian Pelz)
2022-11-19 14:06           ` Joshua Branson via Guix-patches via
2022-12-08 17:02             ` pelzflorian (Florian Pelz)
2023-03-09 21:06       ` pelzflorian (Florian Pelz)
2023-08-20 17:44         ` pelzflorian (Florian Pelz)
2022-10-10  7:57   ` Supported architectures Csepp
2022-10-12 20:40   ` Vagrant Cascadian [this message]
2022-10-13 15:06     ` Ludovic Courtès
2022-10-07  8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09   ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33   ` Efraim Flashner
2022-10-13 15:42   ` Christopher Baines
2022-10-20 13:49   ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07     ` Efraim Flashner
2022-10-21  8:51       ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42         ` Efraim Flashner
2022-10-22 20:22         ` Efraim Flashner
2022-10-26  9:01           ` Efraim Flashner
     [not found]     ` <87h6zyo811.fsf@gnu.org>
2022-10-21  8:43       ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21  9:30         ` Mathieu Othacehe
2022-10-31 17:40         ` Tobias Platen
2022-10-22 12:18     ` Release progress, week 2 Christopher Baines
2022-10-25  9:50     ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29       ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad Christopher Baines

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875ygokc7e.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.org \
    --cc=marius@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.