Add a file documenting known issues.

/trunk/docs/known-issues.txt | 5 5 0 0 +++++
1 file changed, 5 insertions(+)

Do not try to download, extract, or build GMP and MPFR if not asked for.

/trunk/scripts/build/gmp.sh | 12 11 1 0 +++++++++++-
/trunk/scripts/build/mpfr.sh | 11 11 0 0 +++++++++++
2 files changed, 22 insertions(+), 1 deletion(-)

Remove obsolete MPFR version, as it is no longer available for download.

/trunk/config/cc/mpfr.in | 5 0 5 0 -----
1 file changed, 5 deletions(-)

Merge the fortran stuff to trunk now it works!
Fortran is not supported for all targets, though. ARM at least does not work.

/trunk/scripts/build/binutils.sh | 8 8 0 0 ++++++++
/trunk/scripts/build/cc_gcc.sh | 11 6 5 0 ++++++-----
/trunk/scripts/crosstool.sh | 10 9 1 0 +++++++++-
/trunk/tools/addToolVersion.sh | 3 3 0 0 +++
/trunk/steps.mk | 2 2 0 0 ++
/trunk/config/cc/gcc.in | 16 16 0 0 ++++++++++++++++
6 files changed, 44 insertions(+), 6 deletions(-)

Build both shared and static versions of binutils' libraries for target.

/trunk/scripts/build/binutils.sh | 1 1 0 0 +
1 file changed, 1 insertion(+)

Add latest binutils snapshots.

/trunk/config/binutils.in | 12 12 0 0 ++++++++++++
1 file changed, 12 insertions(+)

Do not forget binutils' target libraries in the list.

/trunk/scripts/build/binutils.sh | 4 2 2 0 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Be alittle less verbose in the core CC pass 1 & 2.

/trunk/scripts/build/cc_gcc.sh | 5 0 5 0 -----
1 file changed, 5 deletions(-)

Building target libraries before the cross-compiler is available is doomed! Move build binutils' target libraries after final gcc.
Have a unique list of steps, it's easier to maintain.

/trunk/scripts/build/binutils.sh | 8 5 3 0 +++++---
/trunk/scripts/crosstool.sh | 16 2 14 0 ++--------------
/trunk/steps.mk | 29 16 13 0 ++++++++++++++++-------------
3 files changed, 23 insertions(+), 30 deletions(-)

Eye candy in the binutils config menu.

/trunk/config/binutils.in | 2 1 1 0 +-
1 file changed, 1 insertion(+), 1 deletion(-)