summaryrefslogtreecommitdiff
path: root/misc/buildroot/ReleaseNotes
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-04-13 17:54:59 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-04-13 17:54:59 -0600
commit72a9bdf3ac545e09de89671a5db3a4b6c19d1e1e (patch)
tree08d8934927e29f006cec36485d0ed9a53aea6d9e /misc/buildroot/ReleaseNotes
parent1a552bd8cdbbd50f26a785a1f74b94b29a3be2f6 (diff)
downloadnuttx-72a9bdf3ac545e09de89671a5db3a4b6c19d1e1e.tar.gz
nuttx-72a9bdf3ac545e09de89671a5db3a4b6c19d1e1e.tar.bz2
nuttx-72a9bdf3ac545e09de89671a5db3a4b6c19d1e1e.zip
Removing more trailing whitespace
Diffstat (limited to 'misc/buildroot/ReleaseNotes')
-rw-r--r--misc/buildroot/ReleaseNotes4
1 files changed, 2 insertions, 2 deletions
diff --git a/misc/buildroot/ReleaseNotes b/misc/buildroot/ReleaseNotes
index dce79d50b..e12dd2b49 100644
--- a/misc/buildroot/ReleaseNotes
+++ b/misc/buildroot/ReleaseNotes
@@ -43,8 +43,8 @@ can be used to build the following NuttX-compatible toolchains:
o H8/300 toolchain (not currently used in any NuttX
configuration).
- o i486-elf toochain. Why would you want such a thing? On Linux, of
- course, such a thing is not needed because you can use the installed GCC
+ o i486-elf toochain. Why would you want such a thing? On Linux, of
+ course, such a thing is not needed because you can use the installed GCC
to build i486 ELF binaries. But that will not work under Cygwin! The
Cygwin toolchain (and probably MinGW), build DOS MZ format executables
(i.e., .exe files). That is probably not usable for most NuttX targets.