public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] musl stages for armv5
Date: Sat, 5 May 2018 12:12:55 +0100	[thread overview]
Message-ID: <d55c3283-16f6-a7b0-b15e-fa7788f2b017@iee.org> (raw)
In-Reply-To: <2c7428f5-2f6f-2270-1c84-de9cf4b83e64@longlandclan.id.au>


[-- Attachment #1.1: Type: text/plain, Size: 1246 bytes --]

On 05/05/18 00:19, Stuart Longland wrote:
> Hi all,
>
> I'm slowly pulling together a build of Gentoo/MUSL for ARMv5 machines.
> Right now I've cross-compiled a build environment using OpenADK, thrown
> that onto a Technologic Systems TS-7670, and let it rip.
>
> I've had some set backs, with power black-outs and such, but the build
> is chugging along on the little machine… which has similar
> specifications to the old Cobalt Qube II that I used to use for
> Gentoo/MIPS (mipsel4) stage builds.
>
> CPU: Freescale i.MX286 at 454MHz (1 core)
> RAM: 128MB
> HDD: 1TB SATA via USB 2.0
>
> Gentoo/MUSL is a good fit for these machines I believe due to the low
> RAM footprint, and gcc aside (which takes nearly a week to compile), is
> more manageable on this low-end hardware.
>
> Is there any interest in the stages once they're built?
I'm currently working on some armv6j musl stages also, but talking to
blueness, we might be on our own to 'support' them. That said, I agree
that Musl is a good fit for these lower-power CPUs, and am happy to
share thoughts/rubber-duck if it helps you. If you don't already,
perhaps hang out in #gentoo-arm on Freenode IRC, and we can collate ideas!
Best regards,

Michael.


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

  parent reply	other threads:[~2018-05-05 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 23:19 [gentoo-embedded] musl stages for armv5 Stuart Longland
2018-05-05 11:10 ` Peter Stuge
2018-05-05 11:12 ` M. J. Everitt [this message]
2018-08-22 11:17 ` Stuart Longland

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=d55c3283-16f6-a7b0-b15e-fa7788f2b017@iee.org \
    --to=m.j.everitt@iee.org \
    --cc=gentoo-embedded@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox