From: Ricardo Wurmus <rekado@elephly.net>
To: "André Batista" <nandre@riseup.net>
Cc: Leo Famulari <leo@famulari.name>,
67535@debbugs.gnu.org, guix-devel@gnu.org,
Efraim Flashner <efraim@flashner.co.il>
Subject: Re: Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux]
Date: Thu, 05 Sep 2024 11:42:41 +0200 [thread overview]
Message-ID: <87le06mo6m.fsf@elephly.net> (raw)
In-Reply-To: <ZqlUog2ArfDgEW7N@andel> ("André Batista"'s message of "Tue, 30 Jul 2024 18:02:23 -0300")
André Batista <nandre@riseup.net> writes:
>> > Keeping this to i686-linux specifically, what generation of hardware
>> > supports i686 but not x86_64? Some (very) quick checking on wikipedia
>> > suggests that the x60 from 2006 was either 32-bit or 64-bit, and I
>> > believe there was an atom chip from 2015 that was 32-bit. Specifically,
>> > that makes the newest hardware (at least from the CPU perspective) 10
>> > years old at least.
>>
>> FWIW, I'm using one of those Atom chips in a netbook for an installation
>> of Sugar Desktop. I upgrade it every few months or so. If I'm the only
>> user of i686-linux I would not want to condemn the project to supporting
>> the architecture for my sake.
>
> For the record, I'm another one still using those atom netbooks.
I just noticed that my Atom-powered netbook should also be able to run
an x86_64 system. I'll try to upgrade today; if this is successful I
won't have any i686 system left at home.
--
Ricardo
next prev parent reply other threads:[~2024-09-05 9:43 UTC|newest]
Thread overview: 17+ 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-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 [this message]
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
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=87le06mo6m.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=67535@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=nandre@riseup.net \
/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).