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 File.........: 2 - Installing crosstool-NG.txt
2 Copyrigth....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
3 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
6 Installing crosstool-NG /
7 ________________________/
10 There are two ways you can use crosstool-NG:
11 - build and install it, then get rid of the sources like you'd do for most
13 - or only build it and run from the source directory.
15 The former should be used if you got crosstool-NG from a packaged tarball, see
16 "Install method", below, while the latter is most useful for developpers that
17 use a clone of the repository, and want to submit patches, see "The Hacker's
24 If you go for the install, then you just follow the classical, but yet easy
26 ./configure --prefix=/some/place
29 export PATH="${PATH}:/some/place/bin"
31 You can then get rid of crosstool-NG source. Next create a directory to serve
32 as a working place, cd in there and run:
35 See below for complete usage.
41 If you go the hacker's way, then the usage is a bit different, although very
46 Now, *do not* remove crosstool-NG sources. They are needed to run crosstool-NG!
47 Stay in the directory holding the sources, and run:
50 See below for complete usage.
52 Now, provided you used a clone of the repository, you can send me your changes.
53 See the section titled CONTRIBUTING, below, for how to submit changees.
56 Preparing for packaging |
57 ------------------------+
59 If you plan on packaging crosstool-NG, you surely don't want to install it
60 in your root file system. The install procedure of crosstool-NG honors the
63 ./configure --prefix=/usr
65 make DESTDIR=/packaging/place install
71 crosstool-NG comes with a shell script fragment that defines bash-compatible
72 completion. That shell fragment is currently not installed automatically, but
75 To install the shell script fragment, you have two options:
76 - install system-wide, most probably by copying ct-ng.comp into
77 /etc/bash_completion.d/
78 - install for a single user, by copying ct-ng.comp into ${HOME}/ and
79 sourcing this file from your ${HOME}/.bashrc
85 Some people contibuted code that couldn't get merged for various reasons. This
86 code is available as lzma-compressed patches, in the contrib/ sub-directory.
87 These patches are to be applied to the source of crosstool-NG, prior to
88 installing, using something like the following:
89 lzcat contrib/foobar.patch.lzma |patch -p1
91 There is no guarantee that a particuliar contribution applies to the current
92 version of crosstool-ng, or that it will work at all. Use contributions at