From 7624a19d74882f3b774fdb63a0f6fb507934d9a0 Mon Sep 17 00:00:00 2001 From: patacongo Date: Wed, 2 Dec 2009 23:51:26 +0000 Subject: Add m68hc12 4.3.3 config git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2297 42af7a65-404d-4744-a932-0658087f49c3 --- misc/buildroot/configs/README.txt | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) (limited to 'misc/buildroot/configs/README.txt') diff --git a/misc/buildroot/configs/README.txt b/misc/buildroot/configs/README.txt index 82ddeda9d..bfba22cb4 100644 --- a/misc/buildroot/configs/README.txt +++ b/misc/buildroot/configs/README.txt @@ -60,7 +60,10 @@ h8300_config Builds an H8/300 toolchain using gcc 3.4.5 m68hc11-config - Builds an hc11 toolchain using gcc 3.4.5 + Builds an hc11/hc12 toolchain using gcc 3.4.5 . + +m68hc12-config-4.3.3 + Builds an hc11/hc12 toolchain using gcc 4.3.3. m68k-config Builds an M68K toolchain using gcc 3.4.5 @@ -205,4 +208,10 @@ Cygwin GCC BUILD NOTES the case, it could end-up making a bad toolchain??? In this case, you need to hit Control-C to stop the build. Normally, however, the "Permission denied" error causes the configure script to stop. In either case, if you - just restart the make, the build will continue past the failure point. \ No newline at end of file + just restart the make, the build will continue past the failure point. + + This has happened to me only while doing other intensive activities in + windows during the toolchain build. I suspect if you leave your PC + mostly idle while the toolchain builds, this will not likely be a problem + for you. + -- cgit v1.2.3