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(-)

Adds contrib patch to support the OpenRISK or1k.

/trunk/contrib/openrisc-or32.patch.lzma | 2578 2578 0 0 +++++++++++++++++++++++++++++++++++++++
1 file changed, 2578 insertions(+)

Add building some binutils libraries for the target, as some utilities might need them.

/trunk/scripts/build/binutils.sh | 32 32 0 0 ++++++++++++++++++++++++++++++++
/trunk/config/binutils.in | 22 22 0 0 ++++++++++++++++++++++
2 files changed, 54 insertions(+)

Offer an option to build a static cross-gdb.

/trunk/scripts/build/debug/gdb.sh | 9 9 0 0 +++++++++
/trunk/config/debug/gdb.in | 9 9 0 0 +++++++++
2 files changed, 18 insertions(+)

Document the contrib/ sub-directory.
Fixed the documentation for the arch-dpecific 'CT_DoArchValues' function.

/trunk/docs/overview.txt | 20 13 7 0 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)

Add a directory to store contributed stuff.
It will server to hold unmerged stuff.

Configure tsocks with a simple heuristic.

Consider the proxy has to be in a 'local' network. It means it is directly
reachable by the local machine, even if the local machine has to hop through
one or more gates to reach the proxy (often the case in enterprise networks
where class A 10.0.0.0/8 is in fact sub-divided into smaller networks, each
one of them in a different location, eg. 10.1.0.0/16 in a place, while
10.2.0.0/16 would be on the other side of the world). Not being in the same
subnet does not mean the proxy is not available.

So we will build a mask with at most high bits set, which defines a network
that has both the local machine and the proxy. Because a machine may have
more than one interface, build a mask for each of them, removing 127.0.0.1
which is added automagically by tsocks, and removing duplicate masks.

If all of this does not work, then it means the local machine can NOT in fact
reach the proxy, which in turn means the user mis-configured something (most
probably a typo...).

/trunk/scripts/crosstool.sh | 61 52 9 0 +++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 52 insertions(+), 9 deletions(-)

Tss.... I was bieng real stupid while building up the tsocks.conf file. Implement a much simpler way.

/trunk/scripts/crosstool.sh | 27 5 22 0 +++++----------------------
1 file changed, 5 insertions(+), 22 deletions(-)

Try to make clear that SOCKS proxying is currently BROKEN.

/trunk/config/global/download_extract.in | 36 19 17 0 +++++++++++++++++++-----------------
1 file changed, 19 insertions(+), 17 deletions(-)