libc/glibc: add 2.10.1

Woo... It seems the glibc guys finally decided that tarballs
were not deprecated, in fact.

The patchset was vampirised from Gentoo (kudos, guys!), and
applies to glibc+ports, so that's why it's been added as a
patchset against ports, not against glibc.

scripts: add a new helper script to easily rediff a patchset

scripts: be POSIXly correct in helper scripts

Fix helper scripts to be POSIXly correct: don't expect '.' (the dot
builtin) to search CWD if it is not in $PATH.

scripts: output renumbered patches in a new directory

When renumbering patches, the original patches get removed and replaced
with the new ones. This can be annoying to loose the original patches.
Fix this by putting the new patchs in a directory of their own.

patches/binutils/2.20: make patches appliable

Fix filenames in patch files for binutils-2.20.
Some patch files were only usable with patch argument '-p0'.
Fix the diff context to match 2.20 release.

Signed-off-by: Frederic Roussel <fr.frasc@gmail.com>

scripts: some eye-candy

scripts: update config.{sub,guess}

scripts: fix updating config.{sub,guess}

Merge.

samples: update all samples to the new set of options

No version change is made.

config: mark now old versions as being OBSOLETE

These versions are kept for the upcoming release, but they
will be removed from the next release if they are not used.

config/binutils: add latest version 2.20

Also add patchset vampirised from Gentoo.

debug/strace: add latest version, unmarkprevious EXPERIMENTAL

Also propagate the patchset from 4.5.18 to 4.5.19.

debug/gdb: add latest version 7.0

cc/gcc: add latest 4.4.2 version as EXPERIMENTAL

kernel/linux: add latest versions

binutils: remove duplicate config entries for binutils & elf2flt

scripts: add sed expression to apply when renumbering patches

Some patchsets have superfluous members in their names (eg. the ones coming
from Gentoo), so it can come in handy to pass a sed RE to strip them out of
the final patch name.
Also add a 'fake' mode, where the command will only be printed and not
executed, so we can check beforehand if the rename will be OK.

scripts: fis addToolVersion wrt binutils

binutils' config file has moved; update the addToolVerion script accordingly.

kernel/linux: remove the version prompt

debug/gdb: remove old versions

config/binutils: remove obsolete experimental versions

config: rip-out versions marked as OBSOLETE

libc/uClibc: fix building on system with recent glibc

While trying to build a toolchain with ct-ng 1.5.0,
arm-unknown-linux-uclibcgnueabi target,
I get the following error:

[INFO ] Installing C library headers
[EXTRA] Copying sources to build dir
[EXTRA] Applying configuration
[EXTRA] Building headers
[EXTRA] Installing headers
[ERROR] extra/scripts/unifdef.c:209: error: conflicting types for 'getline'
[ERROR] make[2]: *** [extra/scripts/unifdef] Error 1
[ERROR] Build failed in step 'Installing C library headers'

The following patch solves the problem.
(It's a backport of this uClibc commit:
http://git.uclibc.org/uClibc/commit/?id=49e81cada73616864b9b31df0aeb6961c30f5a6e
)

[--SNIP from another mail--]
AFAIK this is a problem since glibc 2.10.

1.5: update to 1.5.0+hg

Tagging release 1.5.1

1.5: update version to 1.5.1

arch/arm: add sample for nommu bare-metal Cortex-M3 with newlib

arch/arm: add THUMB interworking support

Add config option to build wtarget code with THUMB interworking.
This is used to build the C library as well as all other code
that runs on the target.

arch/arm: add THUMB mode config option