From: "André Batista" <nandre@riseup.net>
To: Leo Famulari <leo@famulari.name>
Cc: Ricardo Wurmus <rekado@elephly.net>,
guix-devel@gnu.org, 67535@debbugs.gnu.org,
Efraim Flashner <efraim@flashner.co.il>
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: Fri, 2 Aug 2024 16:34:31 -0300 [thread overview]
Message-ID: <Zq00x3euWwBFwTw9@andel> (raw)
In-Reply-To: <ZqvsIi7j1EHKkry_@jasmine.lan>
Hi
qui 01 ago 2024 às 16:12:18 (1722539538), leo@famulari.name enviou:
> On Tue, Jul 30, 2024 at 06:02:23PM -0300, André Batista wrote:
> > seg 29 jul 2024 às 14:33:59 (1722274439), rekado@elephly.net enviou:
> > > 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. Most
> > software that I use on that machine still builds and runs fine, with the
> > occasional hiccup.
> >
> > But even though I use the arch, I also don't feel particularly inclined
> > to fix the occasional errors and can understand if people here decide to
> > drop support to it.
>
> Thanks for chiming in Ricardo and André. Do you build your own kernels
> for these machines? Or wait for the occasional successful build from CI?
> Download substitutes from a different build farm?
I build my own kernels tailored for that machine so I did not notice that
substitutes were not available. I usually keep pace with whatever is the
latest stable kernel until it goes eol or, if it is a lts, until the
latest stable reaches x.x.3 or x.x.4 minor version. Currently it is on
v. 6.9.12.
I've not had any issues building kernels to it in a long time, but I do
use two local offload builders that are x84_64. None of them have more
than 8 cores though.
next prev parent reply other threads:[~2024-08-02 19:35 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 ` André Batista [this message]
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
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=Zq00x3euWwBFwTw9@andel \
--to=nandre@riseup.net \
--cc=67535@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=rekado@elephly.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).