# HG changeset patch
# User lost
# Date 1240282657 0
# Node ID 06effa2faea18cd2c447bf41432b5244bd05e4e0
# Parent  0926c29426f48e58107da714255f0cd086a8414a
Added some info on building gcc6809 to use lwtools

diff -r 0926c29426f4 -r 06effa2faea1 extra/README
--- a/extra/README	Tue Apr 21 02:04:57 2009 +0000
+++ b/extra/README	Tue Apr 21 02:57:37 2009 +0000
@@ -20,3 +20,24 @@
 
 Similar to the "as" script above except for lwar.
 
+
+To use these scripts, you really need to understand how to build a gcc as a
+cross compiler. The basics are that you put the as, ld, and ar scripts
+whereever you plan to put your cross-development binaries. Then, when
+building the cross compiler, you tell it where the scripts are.
+
+You should probably name them m6809-unknown-none-{ar,as,ld} or similar
+depending on your gcc build target. Then you'll want to get the gcc6809
+patch and patch the correct gcc source code. Then use a configure line
+similar to the following:
+
+configure --enable-languages=c --target=m6809-coco
+--program-prefix=m6809-coco-lwos- --enable-obsolete
+--srcdir=/home/lost/gcc6809/src/gcc-4.3.3 --disable-threads --disable-nls
+--disable-libssp --prefix=/usr/local/coco --with-as=/usr/local/coco/bin/as
+--with-ld=/usr/local/coco/bin/ld --with-sysroot=/usr/local/coco
+
+Obviously adjust various paths to match what you're doing.
+
+The exact mechanics of configuring and getting gcc to install correctly is
+left as an exercise to the dedicated masochist.