But, if you want to do all the process by hand or you want to build a
Newlib based compiler (not supported yet by crosstool) here is a step
by step guide:

2. Preparing the
installation

Important Note. For building a cross-development tools
based on gcc-3.x it is necessary to have a recent version of gcc
installed on the host workstation. Try to use the latest version
(nowadays: gcc-3.3.1)

Run time library:
Glibc: C run time library for target platforms running linuxcurrent version: glibc-2.3.2
and glibc-linuxthreads-2.3.2.tar.gz
download from: ftp://ftp.gnu.org/gnu/glibc
Newlib: C run time library por embedded devices that does not run
linux
current version: newlib-1.11.0
download from : ftp://sources.redhat.com/pub/newlib

7. Building the runtime
library.

7.1 For Glibc: systems running linux

there is a bug building glibc 2.3.2 with gcc 3.3.1scanf.c in function sscanf
sscanf: 37 error ´va_start´ used in function with fixed argsin order to resolve it edit glibc-2.3.2/stdio-common/sscanf.c
and replace the declaration for sscanf toint sscanf (const char *s, const char *format,
...)

Specify that the target supports AltiVec vector enhancements. This
option will adjust the ABI for AltiVec enhancements, as well as
generate
AltiVec code when appropriate. This option is only available for
PowerPC systems.

10. Using gcc with
altivec extensions

These switches enable or disable the use of built-in functions that
allow access to the AltiVec instruction set. You may also need to set -mabi=altivec
to adjust the current ABI with AltiVec ABI
enhancements.

-mabi=altivec

Extend the current ABI with AltiVec ABI extensions. This does not
change the default ABI, instead it adds the AltiVec ABI extensions to
the current ABI.

If you use a powerpc-*-gnualtivec target-maltivec and
-mabi=altivec are set automatically by the cross-compiler