diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/1 - Introduction.txt | 2 | ||||
| -rw-r--r-- | docs/2 - Installing crosstool-NG.txt | 8 | ||||
| -rw-r--r-- | docs/3 - Configuring a toolchain.txt | 6 | ||||
| -rw-r--r-- | docs/4 - Building the toolchain.txt | 2 | ||||
| -rw-r--r-- | docs/5 - Using the toolchain.txt | 2 | ||||
| -rw-r--r-- | docs/6 - Toolchain types.txt | 2 | ||||
| -rw-r--r-- | docs/8 - Internals.txt | 6 | ||||
| -rw-r--r-- | docs/9 - How is a toolchain constructed.txt | 18 | ||||
| -rw-r--r-- | docs/B - Known issues.txt | 4 | ||||
| -rw-r--r-- | docs/C - Misc. tutorials.txt | 2 | ||||
| -rw-r--r-- | docs/ct-ng.1.in | 4 |
11 files changed, 28 insertions, 28 deletions
diff --git a/docs/1 - Introduction.txt b/docs/1 - Introduction.txt index 3728cbf..15870ab 100644 --- a/docs/1 - Introduction.txt +++ b/docs/1 - Introduction.txt @@ -71,7 +71,7 @@ the new versions, due in part to the big effort it was taking. So I decided to clean up crosstool in the state it was, re-order the things in place, add appropriate support for what I needed, that is uClibc support and a menu-driven configuration, named the new implementation crosstool-NG, -(standing for crosstool Next Generation, as many other comunity projects do, +(standing for crosstool Next Generation, as many other community projects do, and as a wink at the TV series "Star Trek: The Next Generation" ;-) ) and made it available to the community, in case it was of interest to any one. diff --git a/docs/2 - Installing crosstool-NG.txt b/docs/2 - Installing crosstool-NG.txt index 1f85c7b..69909fe 100644 --- a/docs/2 - Installing crosstool-NG.txt +++ b/docs/2 - Installing crosstool-NG.txt @@ -13,7 +13,7 @@ There are two ways you can use crosstool-NG: - or only build it and run from the source directory. The former should be used if you got crosstool-NG from a packaged tarball, see -"Install method", below, while the latter is most useful for developpers that +"Install method", below, while the latter is most useful for developers that use a clone of the repository, and want to submit patches, see "The Hacker's way", below. @@ -50,7 +50,7 @@ Stay in the directory holding the sources, and run: See below for complete usage. Now, provided you used a clone of the repository, you can send me your changes. -See the section titled CONTRIBUTING, below, for how to submit changees. +See the section titled CONTRIBUTING, below, for how to submit changes. Preparing for packaging | @@ -82,12 +82,12 @@ To install the shell script fragment, you have two options: Contributed code | -----------------+ -Some people contibuted code that couldn't get merged for various reasons. This +Some people contributed code that couldn't get merged for various reasons. This code is available as lzma-compressed patches, in the contrib/ sub-directory. These patches are to be applied to the source of crosstool-NG, prior to installing, using something like the following: lzcat contrib/foobar.patch.lzma |patch -p1 -There is no guarantee that a particuliar contribution applies to the current +There is no guarantee that a particular contribution applies to the current version of crosstool-ng, or that it will work at all. Use contributions at your own risk. diff --git a/docs/3 - Configuring a toolchain.txt b/docs/3 - Configuring a toolchain.txt index 092ac0a..1eb6149 100644 --- a/docs/3 - Configuring a toolchain.txt +++ b/docs/3 - Configuring a toolchain.txt @@ -8,7 +8,7 @@ Configuring crosstool-NG / _________________________/ -crosstool-NG is configured with a configurator presenting a menu-stuctured set +crosstool-NG is configured with a configurator presenting a menu-structured set of options. These options let you specify the way you want your toolchain built, where you want it installed, what architecture and specific processor it will support, the version of the components you want to use, etc... The @@ -50,7 +50,7 @@ Interesting config options | ---------------------------+ CT_LOCAL_TARBALLS_DIR: - If you already have some tarballs in a direcotry, enter it here. That will + If you already have some tarballs in a directory, enter it here. That will speed up the retrieving phase, where crosstool-NG would otherwise download those tarballs. @@ -67,7 +67,7 @@ CT_TARGET_VENDOR: Avoid dots, commas, and special characters. CT_TARGET_ALIAS: - An alias for the toolchian. It will be used as a prefix to the toolchain + An alias for the toolchain. It will be used as a prefix to the toolchain tools. For example, you will have ${CT_TARGET_ALIAS}-gcc Also, if you think you don't see enough versions, you can try to enable one of diff --git a/docs/4 - Building the toolchain.txt b/docs/4 - Building the toolchain.txt index 62f0a95..6e24bc0 100644 --- a/docs/4 - Building the toolchain.txt +++ b/docs/4 - Building the toolchain.txt @@ -129,7 +129,7 @@ script is very simple, if not trivial, and works great. The only drawback is that it does not work on host systems that lack a shell, for example the MingW32 environment. To solve the issue, the wrapper has been re-written in C, and compiled at build time. This C wrapper is much more complex than the shell -script, and although it sems to be working, it's been only lightly tested. +script, and although it seems to be working, it's been only lightly tested. Some of the expected short-comings with this C wrapper are; - multi-byte file names may not be handled correctly - it's really big for what it does diff --git a/docs/5 - Using the toolchain.txt b/docs/5 - Using the toolchain.txt index 4d61514..eb8e1aa 100644 --- a/docs/5 - Using the toolchain.txt +++ b/docs/5 - Using the toolchain.txt @@ -41,7 +41,7 @@ run: your-target-tuple-populate -s /your/root -d /your/root-populated This will copy /your/root into /your/root-populated, and put the needed and only -the needed libraries there. Thus you don't polute /your/root with any cruft that +the needed libraries there. Thus you don't pollute /your/root with any cruft that would no longer be needed should you have to remove stuff. /your/root always contains only those things you install in it. 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. diff --git a/docs/8 - Internals.txt b/docs/8 - Internals.txt index 087b18c..816acc6 100644 --- a/docs/8 - Internals.txt +++ b/docs/8 - Internals.txt @@ -32,7 +32,7 @@ ct-ng also searches for config files, sub-tools, samples, scripts and patches in that library directory. Because of a stupid make behavior/bug I was unable to track down, implicit make -rules are disabled: installing with --local would triger those rules, and mconf +rules are disabled: installing with --local would trigger those rules, and mconf was unbuildable. @@ -130,7 +130,7 @@ The architecture's ".sh" file API: - optional - the environment variable CT_TARGET_SYS - contains: - the sytem part of the target tuple. + the system part of the target tuple. Eg.: "gnu" for glibc on most architectures "gnueabi" for glibc on an ARM EABI - defaults to: @@ -159,7 +159,7 @@ The architecture's ".sh" file API: see above. + provides: - optional - - the environement variables to configure the core and final compiler, specific to this architecture: + - the environment variables to configure the core and final compiler, specific to this architecture: - CT_ARCH_CC_CORE_EXTRA_CONFIG : additional, architecture specific core gcc ./configure flags - CT_ARCH_CC_EXTRA_CONFIG : additional, architecture specific final gcc ./configure flags - default to: 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). diff --git a/docs/B - Known issues.txt b/docs/B - Known issues.txt index 4979818..c7ae903 100644 --- a/docs/B - Known issues.txt +++ b/docs/B - Known issues.txt @@ -7,7 +7,7 @@ Known issues / _____________/ -This files lists the known issues encountered while developping crosstool-NG, +This files lists the known issues encountered while developing crosstool-NG, but that could not be addressed before the release. The file has one section for each known issue, each section containing four @@ -136,7 +136,7 @@ Symptoms: Explanations: The gcc build procedure tries to run a Fortran test to see if it has a working native fortran compiler installed on the build machine, and it - can't find one. A native Fortran compiler is needed (seems to be neede) + can't find one. A native Fortran compiler is needed (seems to be needed) to build the Fortran frontend of the cross-compiler. Even if you don't want to build the Fortran frontend, gcc tries to see if it has one, but fails. This is no problem, as the Fortran frontend diff --git a/docs/C - Misc. tutorials.txt b/docs/C - Misc. tutorials.txt index 6fc03da..18d9d2c 100644 --- a/docs/C - Misc. tutorials.txt +++ b/docs/C - Misc. tutorials.txt @@ -275,7 +275,7 @@ In this case, before executing the hg qpush -a from above you should manually "hg qdelete" the patches that are already integrated upstream. -HOW TO FORMAT COMMIT MESSAGES (aka patch desciptions): +HOW TO FORMAT COMMIT MESSAGES (aka patch descriptions): Commit messages should look like (without leading pipes): |component: short, one-line description diff --git a/docs/ct-ng.1.in b/docs/ct-ng.1.in index 6576d34..d711369 100644 --- a/docs/ct-ng.1.in +++ b/docs/ct-ng.1.in @@ -99,7 +99,7 @@ to canonicalise the machines' name (host, build and target machines). Builds a tarball of the generated toolchain, also saving the scripts from .B crosstool-NG that are needed to rebuild the target, and also saving the tarballs of the -componnents that were used. +components that were used. ." .SH ENVIRONMENT .TP @@ -107,7 +107,7 @@ componnents that were used. Respectively stops and restarts the build just before this step. To restart a step, a previous build should have run at least to that step, or further. -The list of steps is vailable with the action +The list of steps is viewable with the action .BR list-steps . ." .SH EXIT VALUE |