| 1 |
On 24/5/19 9:02 am, Joshua Kinard wrote: |
| 2 |
> The stages themselves are |
| 3 |
> based off of a 20190323 portage snapshot (it takes about 2 months to fully |
| 4 |
> build complete stages for six different targets). |
| 5 |
|
| 6 |
Not sure if you're building natively or not… I've found QEMU these days |
| 7 |
runs mips(el)(64) targets decently on modern hardware, as that's what I |
| 8 |
used to bootstrap mips64el n64 stages for Loongson a couple of years ago. |
| 9 |
|
| 10 |
I'm told the same instructions used today hit a bump in the road |
| 11 |
regarding gdbm and gettext bickering about infrastructure ("gettext |
| 12 |
infrastructure mismatch")… evidently a bug that can be reproduced on a |
| 13 |
straight AMD64 system so possibly not a cross-compile bug per-se. I |
| 14 |
think someone who knows more about those two packages than me could |
| 15 |
probably solve it. |
| 16 |
|
| 17 |
I did have a crack at musl, didn't seem to get past first base with |
| 18 |
`crossdev`. |
| 19 |
|
| 20 |
Ultimately that might be the answer though, because let's face it, even |
| 21 |
the Yeeloong doesn't have oodles of RAM and it's not like backward ABI |
| 22 |
compatibility with proprietary glibc-linked applications is a concern on |
| 23 |
MIPS. |
| 24 |
|
| 25 |
Regards, |
| 26 |
-- |
| 27 |
Stuart Longland (aka Redhatter, VK4MSL) |
| 28 |
|
| 29 |
I haven't lost my mind... |
| 30 |
...it's backed up on a tape somewhere. |
Archives