binutils/binutils: do not fwd declare struct stat (2.22).
For canadian cross to host i686-mingw32 fwd declaring
struct stat is not possible.
Instead #include <sys/stat.h>
Signed-off-by: Titus von Boxberg <titus@v9g.de>
Message-Id: <417a15d4277913841ddd.1353100974@tschetwerikow.boxberg.lan>
Patchwork-Id: 199733
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_PROG_NAME@@, crosstool-NG \- Build cross-toolchains
16 .B @@CT_PROG_NAME@@ ACTION
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@@/0 - Table of content.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 Save the current configuration to a mini-defconfig file, that contains only
65 the strictly required symbols to reproduce the configuraiton. defconfig files
66 are much smaller than a complete .config, so it is easy to send by mail. As
67 only non-default symbols are present in a defconfig, it easy to spot the
68 meaningfull values. Also, it is easy to use defconfig files with newer
71 By default the mini-defconfig is saved to a file named
75 is set, in which case the mini-defconfig will be saved to the file referenced
83 is saved. Config files for the components are
93 using a mini-defconfig file (previously saved with
95 or manually edited). The default mini-defconfig is rad from the file
99 is set, inwhich case the mini-defconfig will be read from the file referenced
105 Builds the configured toolchain.
109 Remove files generated by
111 for itself (these are mostly the configurators' binaries).
117 , but also removes the toolchain build directory, the downloaded files and the
119 configuration file. The generated toolchain is left untouched, as well as
120 samples which are not removed.
126 regression test suite. All samples are build, and the regression test suite is
127 run against every one of them.
135 scripts. These scripts are used by
137 to canonicalise the machines' name (host, build and target machines).
140 Builds a tarball of the generated toolchain, also saving the scripts from
142 that are needed to rebuild the target, and also saving the tarballs of the
143 components that were used.
148 Respectively stops and restarts the build just before this step. To restart a
149 step, a previous build should have run at least to that step, or further.
151 The list of steps is viewable with the action
157 frontend is in fact a
159 script. See the man page for
161 to have the meaning of the exit values.
164 As of today (@@CT_DATE@@), building tarballs is broken. It is difficult to
165 foresee how every parts of
167 are going to be installed. Each parts is needed to build a tarball, as it
168 contains all that is needed to rebuild the toolchain from scratch: toolchain
171 configuration, but also all
176 .B Don't run as root!
177 Great care has been taken to avoid mistakes, but bug-free programs don't
178 exist. During normal operation,
180 removes entire directories. If you run as root, and there is a bug or you
183 entire important directories could be removed (eg.
187 will refuse to install toolchains in some well known critical directories.
190 Please consult the file
191 .I @@CT_DOCDIR@@/CREDITS
192 for a list of contributors.
195 You can find more in-depth documentation in
196 .IR "@@CT_DOCDIR@@/0 - Table of content.txt" .
198 Please have a look at the
199 .URL "http://www.kegel.com/crosstool" "original crosstool" " by Daniel KEGEL"