debug/gdb: fix for psim build failure due to -lz in gdb-7.2.
Signed-off-by: "Horst Kronstorfer" <horst.kronstorfer@aon.at>
[yann.morin.1998@anciens.enib.fr: fix space-damage]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 78286fe70b62cee395bc603a5e44ef136c4531e3)
1 ." crosstool-NG man page
2 ." Copyright 2007 Yann E. MORIN
3 ." Licensed under the Creative Commons BY-SA, v2.5
8 .TH crosstool-NG 1 "@@CT_DATE@@" "version @@CT_VERSION@@" "User Commands"
12 ct-ng, crosstool-NG \- Build cross-toolchains
20 Building a cross-toolchain can be a real pain.
23 makes it easy to build cross-toolchains, and allows you to take all the juice
24 out of your target by configuring the different components of the toolchain
25 accordingly to the targeted processor.
29 Here are the most commonly used actions. For other actions, please see
30 .I @@CT_DOCDIR@@/overview.txt
33 Prints a little help text.
39 using a configurator menu very similar to that of the Linux kernel.
43 Apply options found in an existing
45 file, and ask for newer options if there are any.
51 configuration, and associated components' config files, into a sample. Samples
52 are saved in their own sub-directory, named after the target's tuple, in the
54 sub-directory of the current directory.
55 If that was not clear:
56 .I `pwd`/samples/${CT_TARGET}/
58 Samples can be later recalled by calling
60 with the target tuple they represent.
64 Builds the configured toolchain.
68 Remove files generated by
70 for itself (these are mostly the configurators' binaries).
76 , but also removes the toolchain build directory, the downloaded files and the
78 configuration file. The generated toolchain is left untouched, as well as
79 samples which are not removed.
85 regression test suite. All samples are build, and the regression test suite is
86 run against every one of them.
94 scripts. These scripts are used by
96 to canonicalise the machines' name (host, build and target machines).
99 Builds a tarball of the generated toolchain, also saving the scripts from
101 that are needed to rebuild the target, and also saving the tarballs of the
102 componnents that were used.
107 Respectively stops and restarts the build just before this step. To restart a
108 step, a previous build should have run at least to that step, or further.
110 The list of steps is vailable with the action
116 frontend is in fact a
118 script. See the man page for
120 to have the meaning of the exit values.
123 As of today (@@CT_DATE@@), building tarballs is broken. It is difficult to
124 foresee how every parts of
126 are going to be installed. Each parts is needed to build a tarball, as it
127 contains all that is needed to rebuild the toolchain from scratch: toolchain
130 configuration, but also all
135 .B Don't run as root!
136 Great care has been taken to avoid mistakes, but bug-free programs don't
137 exist. During normal operation,
139 removes entire directories. If you run as root, and there is a bug or you
142 entire important directories could be removed (eg.
146 will refuse to install toolchains in some well known critical directories.
149 Please consult the file
150 .I @@CT_DOCDIR@@/CREDITS
151 for a list of contributors.
154 You can find more in-depth documentation in
155 .IR @@CT_DOCDIR@@/overview.txt .
157 Please have a look at the
158 .URL "http://www.kegel.com/crosstool" "original crosstool" " by Daniel KEGEL"