================
- What This Is -
================

Contained herein are stages for an N32 MIPS Userland.  These are
HIGHLY experimental, and should only be used by people who meet
the following criteria:
	A) Currently run an O32 Gentoo/MIPS Install and
	   are familiar with operating in a Gentoo Environment

	B) Are familiar with the various MIPS ABIs and the
	   differences between them (i.e., o32, o64, n32, n64)

	C) Are willing to deal with the possibility that the
	   userland provided by these stages may
		i)	Work
		ii)	Not Work
		iii)	Not Work and eat kittens

	D) Are willing to diagnose and report (as bugs) problems
	   that may seem very odd or do very weird things



==============
- How To Use -
==============

Simply download and use the stage as you would in a normal Gentoo/MIPS
install, except for the following changes:
	A) The system being installed with an N32 Userland MUST be a
	   mips64 system, which currently include:
		i)	SGI O2 (IP32)
		ii)	SGI Octane (IP30)
		iii)	SGI Indigo2 Impact R10000 (IP28)
		iv)	SGI Origin (IP27)*
		v)	SGI Indy/Indigo2 R4x00 (IP22) [w/ mips64 kernel]**

		*)	IP27 Doesn't work correctly with newer kernel revisions
		**)	IP22 mips64 isn't a fully supported configuration

	B) Use the following profile:
		/usr/portage/profiles/default-linux/mips/mip64/n32/2005.0



=================================
- What To Do If Something Break -
=================================

First of all, Don't Panic.

Second, chew on the corner of your towel.  It has valuable vitamins and nutrients.

Third, determine the nature of the failure:
	A) Is it a fault or bug in the experimental nature of N32?
	B) Is is a fault or bug because of what a developer (Us) did?
	C) Is it a fault or bug because of something I (you) did?
	D) Is it a fault or bug because of Random Acts of God?

If (A), then the solution could be unknown.  The solution could require a patch
to the offending program, to the compiler, to glibc, or even to the headers.

If (B), then file a bug, and include support information so we know what we
did wrong, and so we know exactly what to fix.

If (C), then make sure you're not using overzealous CFLAGS, LDFLAGS, or even ASFLAGS;
Cut back on your MAKEOPTS if you use -jX, Make sure you're using the correct profile
and most importantly, ACCEPT_KEYWORDS="~mips" in /etc/make.conf (N32 will be "unstable"
for a very long time to come)

If (D), then consider getting your system exorcised.  I would advise against sprinkling
holy water on it, as that could release the magic blue smoke.