# HG changeset patch
# User lost
# Date 1259269948 0
# Node ID b3407101340462187c60502017dce0c95c593ac7
# Parent  e8d70b95ec41da4033e192a8cf5dea4b1f424026
Updated hint for using gcc6809

diff -r e8d70b95ec41 -r b34071013404 extra/README
--- a/extra/README	Sun Nov 22 05:46:31 2009 +0000
+++ b/extra/README	Thu Nov 26 21:12:28 2009 +0000
@@ -27,9 +27,10 @@
 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:
+depending on your gcc build target.  You will probably need to ensure that
+the m6809-* binaries are in your execution path.  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