summaryrefslogtreecommitdiff
path: root/docs/9 - How is a toolchain constructed.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/9 - How is a toolchain constructed.txt')
-rw-r--r--docs/9 - How is a toolchain constructed.txt18
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/9 - How is a toolchain constructed.txt b/docs/9 - How is a toolchain constructed.txt
index 3290f0d..cc8e6a6 100644
--- a/docs/9 - How is a toolchain constructed.txt
+++ b/docs/9 - How is a toolchain constructed.txt
@@ -50,13 +50,13 @@ into actual executable code. Depending on the Operating System, or the lack
thereof, running on the target, we also need the C library. The C library
provides a standard abstraction layer that performs basic tasks (such as
allocating memory, printing output on a terminal, managing file access...).
-There are many C libraries, each targetted to different systems. For the
-Linux /desktop/, there is glibc or eglibc or ven uClibc, for embeded Linux,
+There are many C libraries, each targeted to different systems. For the
+Linux /desktop/, there is glibc or eglibc or even uClibc, for embedded Linux,
you have a choice of eglibc or uClibc, while for system without an Operating
System, you may use newlib, dietlibc, or even none at all. There a few other
-C libraries, but they are not as widely used, and/or are targetted to very
+C libraries, but they are not as widely used, and/or are targeted to very
specific needs (eg. klibc is a very small subset of the C library aimed at
-building contrained initial ramdisks).
+building constrained initial ramdisks).
Under Linux, the C library needs to know the API to the kernel to decide
what features are present, and if needed, what emulation to include for
@@ -168,7 +168,7 @@ is not too recent, chances are that we will have to build those libraries
correct rounding, MPFR
- the C library for the arithmetic of complex numbers, MPC
-The dependencies for those liraries are:
+The dependencies for those libraries are:
- MPC requires GMP and MPFR
- MPFR requires GMP
@@ -205,7 +205,7 @@ To enable GRAPHITE:
To enable LTO:
- the ELF object file access library, libelf
-The depencies for those libraries are:
+The dependencies for those libraries are:
- PPL requires GMP
- CLooG/PPL requires GMP and PPL
@@ -233,7 +233,7 @@ This list is now complete! Wouhou! :-)
So the list is complete. But why does crosstool-NG have more steps? |
--------------------------------------------------------------------+
-The already thirteen steps are the necessary steps, from a theorical point
+The already thirteen steps are the necessary steps, from a theoretical point
of view. In reality, though, there are small differences; there are three
different reasons for the additional steps in crosstool-NG.
@@ -249,9 +249,9 @@ libc_finish step.
Third, crosstool-NG can also build some additional debug utilities to run on
the target. This is where we build, for example, the cross-gdb, the gdbserver
-and the native gdb (the last two run on the target, the furst runs on the
+and the native gdb (the last two run on the target, the first runs on the
same machine as the toolchain). The others (strace, ltrace, DUMA and dmalloc)
are absolutely not related to the toolchain, but are nice-to-have stuff that
-can greatly help when developping, so are included as goodies (and they are
+can greatly help when developing, so are included as goodies (and they are
quite easy to build, so it's OK; more complex stuff is not worth the effort
to include in crosstool-NG).