README
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Jun 11 21:47:19 2009 +0000 (2009-06-11)
changeset 1352 d7ddcb75e0f7
parent 1335 4a5540d3a301
child 1463 de40924df7b4
permissions -rw-r--r--
populate: fix installing dynamic linker 'ld.so'

The dynamic linker, ld.so, needs the execute bit to be set.
Detect tht the library being installed is in fact ld.so and
install it with 0755 instead of 0644.

Fix detecting src == dst.

Use a simpler command to copy src -> dst.

Also change echo to printf, get rid of 'echo -n', which is
highly non-portable.


-------- diffstat follows --------
/trunk/scripts/populate.in | 76 43 33 0 +++++++++++++++++++++++++++++-----------------------
1 file changed, 43 insertions(+), 33 deletions(-)
yann@1
     1
This is the README for crosstool-NG
yann@1
     2
yann@88
     3
To get you started, just enter:
yann@185
     4
  ./configure --help
yann@1
     5
yann@185
     6
You can find a (terse and WIP) documentation in docs/overview.txt.
yann@1
     7
yann@1
     8
You can also point your browser to
yann@88
     9
  http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool
yann@96
    10
yann@1335
    11
If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
yann@1335
    12
yann@185
    13
If you need to send a bug report or a patch, please send a mail with subject
yann@386
    14
prefixed with "[CT_NG]" with the following destinations:
yann@764
    15
    TO: yann.morin.1998 (at) anciens.enib.fr
yann@764
    16
    CC: crossgcc (at) sourceware.org
yann@386
    17
yann@1348
    18
Patches should come with the appropriate SoB line. A SoB line is typically
yann@1348
    19
something like:
yann@1348
    20
  Signed-off-by: John DOE <john.doe@somewhere.net>
yann@1348
    21
yann@1348
    22
The SoB line is clearly described in Documentation/SubmittingPatches , section
yann@1348
    23
12, of your favourite Linux kernel source tree.
yann@1348
    24
yann@386
    25
The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
yann@185
    26
yann@908
    27
The list of known issues is listed in docs/known-issues.txt.
yann@817
    28
yann@185
    29
Aloha!