From: Stuart Longland <stuartl@longlandclan.id.au>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] I tarballed a full gentoo system image for the SGI Octane
Date: Sun, 20 Oct 2019 17:41:29 +1000 [thread overview]
Message-ID: <1d2993f3-acd6-4366-8e35-41ef04cc6ec4@longlandclan.id.au> (raw)
In-Reply-To: <2f239868-da0e-31a2-96c2-d8419e6bd7f1@gentoo.org>
On 24/5/19 9:02 am, Joshua Kinard wrote:
> The stages themselves are
> based off of a 20190323 portage snapshot (it takes about 2 months to fully
> build complete stages for six different targets).
Not sure if you're building natively or not… I've found QEMU these days
runs mips(el)(64) targets decently on modern hardware, as that's what I
used to bootstrap mips64el n64 stages for Loongson a couple of years ago.
I'm told the same instructions used today hit a bump in the road
regarding gdbm and gettext bickering about infrastructure ("gettext
infrastructure mismatch")… evidently a bug that can be reproduced on a
straight AMD64 system so possibly not a cross-compile bug per-se. I
think someone who knows more about those two packages than me could
probably solve it.
I did have a crack at musl, didn't seem to get past first base with
`crossdev`.
Ultimately that might be the answer though, because let's face it, even
the Yeeloong doesn't have oodles of RAM and it's not like backward ABI
compatibility with proprietary glibc-linked applications is a concern on
MIPS.
Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
prev parent reply other threads:[~2019-10-20 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 22:42 [gentoo-mips] I tarballed a full gentoo system image for the SGI Octane Florian 'rephlex' Panzer
2019-05-23 23:02 ` Joshua Kinard
2019-10-20 7:41 ` Stuart Longland [this message]
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=1d2993f3-acd6-4366-8e35-41ef04cc6ec4@longlandclan.id.au \
--to=stuartl@longlandclan.id.au \
--cc=gentoo-mips@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