$NetBSD: README.FIRST,v 1.5 1997/04/20 20:46:49 thorpej Exp $

Parts of this toolchain are alpha- or beta-test code.

If you run into any problems with this toolchain, please send them to
cgd-toolchain@netbsd.org, NOT the standard GNU toolchain bug-reporting
places.

Versions:

	binutils	gas 970416 snapshot
	bison		1.25
	gcc		2.7.2.2
	gdb		4.16
	texinfo		3.9
	psim		psim 970312 snapshot

(all except bison have local patches applied)

Note: You must have GNU gperf installed on your system to build this
toolchain!  You may get GNU gperf from the libg++ 2.7.2 distribution,
available at your favorite GNU mirror.  Unfortunately, integrating gperf
into this package would be a complex task, due to the build system it
uses in the libg++ tree.  Until this is resolved, you must install
gperf separately.



PowerPC users:

To configure this toolchain for NetBSD/powerpc, use:

	./configure --target=powerpc-unknown-netbsd

The default executable format is elf32-powerpc, using the SVR4 calling
conventions.

The PowerPC simulator PSIM, which runs inside of GDB, may be enabled
with the --enable-sim-powerpc option.  Recommended PSIM options are:

	--enable-sim-endian=big
	--enable-sim-trace
	--enable-sim-float
	--enable-sim-inline=no

If you build the simulator on a PC with an i486 or greater CPU, you may
use --enable-sim-bswap to reduce code size and improve performance.

If you have a system with a large amount of memory and swap (128M RAM, at
least 256M swap), you may --enable-sim-inline=yes.  The simulator's
performance will increase, but with a substantial penalty in compile time
(and compiler resident size!) and simulator executable size.

Documentation on the PSIM PowerPC simulator may be found at:

	http://www.cygnus.com/~meissner/psim.html



Internal maintenance stuff:

Commands like:

	mkdir toolchain

	mkdir toolchain/bison
	(cd bison-1.25 ; tar cf - .) | (cd toolchain/bison ; tar xf -)

	mkdir toolchain/gcc
	(cd gcc-2.7.2.2 ; tar cf - .) | (cd toolchain/gcc ; tar xf -)

	mkdir toolchain/texinfo
	(cd texinfo-3.9 ; tar cf - .) | (cd toolchain/texinfo ; tar xf -)

	(cd gdb-4.16 ; tar cf - .) | (cd toolchain ; tar xf -)
	rm -rf toolchain/bfd toolchain/libiberty toolchain/opcodes

	(cd gas-970416 ; tar cf - .) | (cd toolchain ; tar xf -)

can be used to integrate a new toolchain.  Note that new versions don't have
to be imported 'whole', i.e. individual pieces can be imported seperately.
Note, however, that if you're going to import a new version of gdb, you
probably should kill its versions of bfd, libiberty, and opcodes.  Indeed, it's probably better to do them seperately.

All sources have a vendor tag of 'fsf'.  Single pieces, when imported alone,
have release tags like 'fsf-progname-progmajver-progminver[...]'.  When
multiples pieces are imported together, the tags get weirder.  That's why
it's probably better to do them seperately.

The file CLEANLIST contains the names of files which should be rm'd after
a 'make distclean' to get a clean "cvs update".
