Gentoo Archives: gentoo-mips

From: Stuart Longland <redhatter@g.o>
To: gentoo-mips@l.g.o
Cc: gentoo-mips@l.g.o
Subject: Re: [gentoo-mips] profiles
Date: Thu, 01 Sep 2005 01:49:53
Message-Id: 51067.131.181.46.59.1125539368.squirrel@mail.longlandclan.hopto.org
In Reply to: Re: [gentoo-mips] profiles by Curtis Phillips
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Curtis Phillips _top posted_:
> I'd prefer Kumba's machine specific profiles. Of course, that's the one > that's the biggest PITA to implement/update. > > Curtis Phillips > Winemaker > Salmon Leap Consulting > > On Aug 30, 2005, at 8:18 AM, Stephen P. Becker wrote: > >> D) (Kumba's idea here...) Have machine specific profiles, e.g. >> default-linux/mips/ip22, default-linux/mips/ip32, etc. (This could be >> really useful because it would allow us to do some other machine >> specific voodoo in the profile). >> >> Any thoughts?
I was thinking that perhaps we could also split it into Endianness, for CHOST voodoo, and anything else that's endianness-sensitive. So the profiles would become;
> /usr/profiles/default-linux/mips: > |- be -- Big Endian Systems > | |- n32 \__ Profile for any 64-bit voodoo > | |- n64 / > | |- ip22 -- SGI Indy, Indigo2 (R4k), Challenge S w/ o32 > | | |= n32 -- importing the ../n32 voodoo > | | |- n64 -- importing the ../n64 voodoo > | | '- 2.4 -- with kernel 2.6 stuff masked (for R4600) > | | > | |- ip27 -- SGI Origin 200/2000 w/ o32 > | | |- n32 -- importing the ../n32 voodoo > | | '- n64 -- importing the ../n64 voodoo > | | > | |- ip28 -- SGI Indigo2 Impact (R10000) > | | |- n32 -- as above > | | '- n64 > | | > | |- ip30 -- SGI Octane/Octane 2 > | | |- n32 > | | '- n64 > | | > | '- ip32 -- SGI O2 > | |- r10k -- For R10k-based O2s, if support existed. > | | |- n32 > | | '- n64 > | |- n32 > | '- n64 > '- le -- Little Endian > |- n32 > |- n64 > |- cobalt > | |- n32 > | '- n64 > '- amdalchemy
The above is just an idea. The main reason for splitting 'le' and 'be' is so that the CHOST can be set correctly (mips{,64}-unknown-linux-gnu on be, mips{,64}el-unknown-linux-gnu on le). As for how to handle µClibc, not sure there. I'm guessing it'd be another profile like n32, just to s/gnu/uclibc/ in the CHOST -- certainly it will be that way whilst it's o32 only. Anyways, those are my thoughts. :-) - -- : ____ _ Stuart Longland (a.k.a Redhatter) :/ \ ___ ___ __| |__ __ __ Gentoo Linux/MIPS Cobalt and Docs :- ( ) \ / \ ; \(__ __)/ \ / \ Developer : \ // O _| / /\ \ | | | /\ | /\ | : / / \ /__| / \ \ | | | \/ | \/ | :(___/ \____/|_; |_| \_/ \__/ \__/ http://dev.gentoo.org/~redhatter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDFl4ouarJ1mMmSrkRAiDCAJ42KOIXnKwRBvvojDdexE07NF9BIACePZVz bwMsxOxp1aIv5jPfWyAsnV8= =3zEt -----END PGP SIGNATURE----- -- gentoo-mips@g.o mailing list

Replies

Subject Author
Re: [gentoo-mips] profiles Stephen Bennett <spb@g.o>