From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 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: Fri, 26 Jul 2024 20:17:40 +0000 [thread overview]
Message-ID: <jomhG_vudfQ-fyVVYlPIXpbcCylT1znYR-ywuW9PSUG_xv_YHNITY1CWMQMVfYUmoji56WZEZEs3cOCifIWUyr5gWIsYCCPSfzek2ap75wI=@protonmail.com> (raw)
In-Reply-To: <ZqPwRe6ylRgGAeW1@jasmine.lan>
Hi,
On Friday, July 26th, 2024 at 11:51 AM, Leo Famulari <leo@famulari.name> 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'm forwarding this bug to guix-devel to get more attention.
>
> Is anybody actually using i686-linux anymore? Or should we begin to
> officially remove support for it?
I'm not sure about i686-linux's usage for a complete system (and I know several other distributions either already have or have plans to drop support for booting 32-bit x86 systems), but at least the "multi-lib" portion of i686-linux packages are needed for the wine and wine64 packages (and their "-staging" variants) on x86_64-linux systems.
Cheers,
Kaelyn
next prev parent reply other threads:[~2024-07-26 20:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 20:55 bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux Leo Famulari
2023-12-06 12:25 ` Efraim Flashner
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 [this message]
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-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
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='jomhG_vudfQ-fyVVYlPIXpbcCylT1znYR-ywuW9PSUG_xv_YHNITY1CWMQMVfYUmoji56WZEZEs3cOCifIWUyr5gWIsYCCPSfzek2ap75wI=@protonmail.com' \
--to=kaelyn.alexi@protonmail.com \
--cc=67535@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.