diff options
| author |   Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> | 2011-07-17 14:53:40 (GMT) |
|---|---|---|
| committer |   Antony N. Pavlov" <antony@niisi.msk.ru> | 2011-07-17 14:53:40 (GMT) |
| commit | c009897aeec4ac3265498664937b2b86870b9984 (patch) | |
| tree | 046538459cc0fffed04c7483331db2bd0a76ab35 /docs/6 - Toolchain types.txt | |
| parent | 30ad622618504b5801ae06a4f28ebd0d10655648 (diff) | |
misc: fix more typos here and there...
Reported-by: "Antony N. Pavlov" <antony@niisi.msk.ru>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Diffstat (limited to 'docs/6 - Toolchain types.txt')
| -rw-r--r-- | docs/6 - Toolchain types.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/6 - Toolchain types.txt b/docs/6 - Toolchain types.txt index 3e3b3df..382ceb6 100644 --- a/docs/6 - Toolchain types.txt +++ b/docs/6 - Toolchain types.txt @@ -30,7 +30,7 @@ Any toolchain will involve those three machines. You can be as pretty sure of this as "2 and 2 are 4". Here is how they come into play: 1) build == host == target - This is a plain native toolchain, targetting the exact same machine as the + This is a plain native toolchain, targeting the exact same machine as the one it is built on, and running again on this exact same machine. You have to build such a toolchain when you want to use an updated component, such as a newer gcc for example. |