README
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Sep 22 12:09:19 2008 +0000 (2008-09-22)
changeset 866 5fec4dba671e
parent 764 ff368787f62b
child 908 6db1117b2893
permissions -rw-r--r--
Add binutils-2.18.50.0.9.
Add a patch to binutils to not use '/' as a comment separator on i386 assembly when targeting bare metal (breaks linux kernel build).

/trunk/patches/binutils/2.18.50.0.8/130-i386-no-divide-comment.patch | 64 64 0 0 ++++++++++
/trunk/patches/binutils/2.18.50.0.9/130-i386-no-divide-comment.patch | 64 64 0 0 ++++++++++
/trunk/patches/binutils/2.14/110-i386-no-divide-comment.patch | 38 38 0 0 ++++++
/trunk/patches/binutils/2.14/270-i386-no-divide-comment.patch | 38 38 0 0 ++++++
/trunk/patches/binutils/2.16.1/160-i386-no-divide-comment.patch | 40 40 0 0 ++++++
/trunk/patches/binutils/2.17/210-i386-no-divide-comment.patch | 64 64 0 0 ++++++++++
/trunk/patches/binutils/2.18/120-i386-no-divide-comment.patch | 64 64 0 0 ++++++++++
/trunk/patches/binutils/2.18.50.0.4/130-i386-no-divide-comment.patch | 64 64 0 0 ++++++++++
/trunk/patches/binutils/2.18.50.0.6/130-i386-no-divide-comment.patch | 64 64 0 0 ++++++++++
/trunk/patches/binutils/2.18.50.0.7/130-i386-no-divide-comment.patch | 64 64 0 0 ++++++++++
/trunk/config/binutils.in | 6 6 0 0 +
11 files changed, 570 insertions(+)
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@185
    11
If you need to send a bug report or a patch, please send a mail with subject
yann@386
    12
prefixed with "[CT_NG]" with the following destinations:
yann@764
    13
    TO: yann.morin.1998 (at) anciens.enib.fr
yann@764
    14
    CC: crossgcc (at) sourceware.org
yann@386
    15
yann@386
    16
The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
yann@185
    17
yann@817
    18
The list of known issues is listed in docs.known-issues.txt.
yann@817
    19
yann@185
    20
Aloha!