changeset 249:b34071013404 2.x

Updated hint for using gcc6809
author lost
date Thu, 26 Nov 2009 21:12:28 +0000
parents e8d70b95ec41
children 0986834ec7d3
files extra/README
diffstat 1 files changed, 4 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- 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