public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Longland <redhatter@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] bootstrap.sh on asus wl500g
Date: Sat, 17 Sep 2005 00:02:21 +1000	[thread overview]
Message-ID: <432AD06D.7020205@gentoo.org> (raw)
In-Reply-To: <432ACE12.2040600@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

Hardave Riar wrote:
> Jason Pepas wrote:
> 
>> and the profile like so:
>>
>>     make.profile -> /usr/portage/profiles/default-linux/mips/2005.0
> 
> 
> That's the wrong profile for uclibc stages, this will try to replace
> uclibc with glibc and that's a bad thing. You should probablly be using
> /usr/portage/profile/uclibc/mips. Using the uclibc stages it should not
> try to build glibc like it is below.
> 
>> any ideas?  I see the mips project website was just updated today, and I
>> just realized last night that the cobalt images are little endian (the
>> asus wl500g is little endian), so I'll try chrooting into one of those
>> images next.
> 
> 
> Don't bother using the cobalt stages, the wl500g has no where near
> enough memory to run a glibc system.

Not to mention, the Cobalt stages are MIPS IV, and therefore includes
some 64-bit instructions, the WL500g will be MIPS32, and does not
understand 64-bit instructions.

So you can expect illegal instructions left, right & centre.

As Stephen has pointed out too, messing with CHOST is asking for it... I
speak from experience. :-)
(tried it on my x86-based laptop ... boy did I have fun finding the
pieces and putting them back together again :-/)
-- 
 ____                   _             Stuart Longland (a.k.a Redhatter)
/  _ \   ___    ___  __| |__  __   __ Gentoo Linux/MIPS Cobalt and Docs
- (_) \ /   \  ;   \(__   __)/  \ /  \                        Developer
 \    //  O _| / /\ \  | |  | /\ | /\ |
 /   / \   /__| /  \ \ | |  | \/ | \/ |
(___/   \____/|_;  |_| \_/   \__/ \__/ http://dev.gentoo.org/~redhatter

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

  reply	other threads:[~2005-09-16 14:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 13:34 [gentoo-mips] bootstrap.sh on asus wl500g Jason Pepas
2005-09-16 13:42 ` Jason Pepas
2005-09-16 13:48   ` Jason Pepas
2005-09-16 13:48 ` Stephen P. Becker
2005-09-16 13:52   ` Stephen P. Becker
2005-09-16 14:01   ` Jason Pepas
2005-09-16 14:28     ` Stephen P. Becker
2005-09-16 14:44       ` Jason Pepas
2005-09-16 15:44         ` Hardave Riar
2005-09-16 16:28           ` Jason Pepas
2005-09-16 19:00           ` Stephen P. Becker
2005-09-16 13:52 ` Hardave Riar
2005-09-16 14:02   ` Stuart Longland [this message]
2005-09-16 14:07   ` Jason Pepas
2005-09-16 14:25     ` Stephen P. Becker
2005-09-16 14:39       ` Jason Pepas
2005-09-16 15:37         ` Hardave Riar
2005-09-16 15:53           ` Jason Pepas

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=432AD06D.7020205@gentoo.org \
    --to=redhatter@gentoo.org \
    --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