[configure] Use hg, instead of svn, to compute the version string

Now we moved from Subversion to Mercurial, use the hg command to
compute the version string.

Manually backported from 1409:7264ce426be4 plus 1430:933eee133cbf
as too much changes have been made to ./configure in the meantime.

[complib:mpfr] Fix building MPFR in some weird cases

The tmul test uses a compiled-in input file in $(srcdir).
The problem is that the Makefile passes it unquoted. The C code
tries to stringify it using clever macros, which may *usually* work.

In my case the source directory was named:
.../toolchain-powerpc-e500v2-linux-gnuspe-1.0-2.fc10/.../tests
And guess what? During testing I found out the program fails because
it tries to open:
.../toolchain-powerpc-e500v2-1-gnuspe-1.0-2.fc10/.../tests

Yes, CPP tokenized the macro before stringifying it and not surprisingly
the 'linux' part was converted to 1.
[on Fedora-10: cpp (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)]

So the attached patch simplify the macros and pass the path as string
from the Makefile.

[config] Merge CONFIG_SHELL selection.

[config] Warn againt using ash as CONFIG_SHELL

It apears that more and more ./configure scripts and Makefiles
make use of non-POSIXly correct shell constructs, that don't
work with ash.

For now, just warn the user against using ash, but keep it as
an option in case newer versions of the /broken/ components
come fixed, and we can again use ash, as it is in some cases
really faster than bash.

[config] Allow user to specify custom CONFIG_SHELL

In case the shell the user wants to use as CONFIG_SHELL is located in a
weird place (eg. /opt/bash/bin/bash), or is weirdly named (eg. bash-4),
let the user enter the patch to the shell.

[config] Add bash as a possible CONFIG_SHELL

On some systems and/or for some components, it may be necessary to
explicitly use bash as the shell used by ./configure and Makefiles.

[config] Change the way to select the CONFIG_SHELL

Transform the single boolean option to a 'choice' selection
with two options: "sh" and "ash".

This is needed to later add "bash" as override.

Merge the queue with all new component versions.

[cc-gcc] Add latest versions

Add gcc-4.4.1

[scripts-add-version] Handle gcc 4.4+

Handle gcc-4.4+ when adding a new gcc version.

[comp-lib-gmp] Add latest versions

Add 4.3.0 and 4.3.1.

[tools-libelf] Add latest version.

Add libelf 0.8.11, propagate patchset from 0.8.10.

[libc-eglibc] Add latest version

Add latest branch 2_10.

[debug-ltrace] Add latest version.

Add ltrace 0.5.2, propagate patchset from 0.5.1 and from Debian.

[debug-duma] Add latest versions

Add 2.5.15, propagate patchset from 2_5_14 up to 2_5_15.

[kernel-linux] Add latest versions

Add 2.6.29.{5,6} and 2.6.30{,.1}
Update 2.6.27.24 to 2.6.27.26 as long-term stable.

fix wrapper script for symlinks

The wrapper script placed around the target binaries when
using the companion libraries does not work for symbolic links
The wrapper scripts needs to follow the links before calling the
actual binary

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>

---

Add g++ to required tools

Because gmp is now always build with --enable-cxx,
g++ has become a required tool

Signed-off-by: Bart vdr Meulen <bartvdrmeulen@gmail.com>

---

[configure] Fix automake version check.

The configure script fails on automake-1.11 (in Fedora-11) since
it looks for 3-digit version number.

Patch fixed by "Yann E. MORIN", with the added comment:

The check for the automake version is not against a 3-digit number,
but really against a 3-part version number, a-la 'x.y.z'. Versions
such as 1.10 and 1.11 are also valid.

Require GNU awk at ./configure time.

Some components (specifically {,e}glibc) will not build when awk
is not GNU awk. Make ./configure check for GNU awk.

Make it build again for non-local use.

Using colons (:) in the version string creates Makefile problems:

Makefile:195: *** multiple target patterns. Stop.
make: *** [build] Error 2

Merge the canadian branch to default.

Now the preliminray support for canadian-crosses is done,
merge to default. The few remaining quirks, if any, will
be resolved on mainstream.

[samples] Add a linux -> mingw32 -> i686-linux canadian sample

Add a sample that builds on Linux a mingw32-hosted toolchain that
generates code for i686-none-linux-gnu.

Signed-off-by: Bart van der Meulen <bartvdrmeulen@gmail.com>

[samples] Don't mix canadian samples with non-canadian ones.

- save the canadian smples in their own way, so as not to
mix non-canadian samples with canadian ones
- list canadian samples with the host information

Cleanup the handling of canadian settings

Bring handling the 'canadian' settings as par with the existing
'cross' settings.

Add support code for the canadian-cross case.

Add implementation for a candadian build option already
present in crosstool in order to build a cross-compiler
where build != host != target

Signed-off-by: Bart van der Meulen <bartvdrmeulen@gmail.com>

[samples] Make saveSample.sh a little bit more generic

Prepare saving canadian samples by making the saveSample.sh script
a little bit more generic, using conditional code-paths (even if
there's currently a single code-path).

Don't use prefix/bin to install the buildtools.

Collect the build tools in a seperate folder in order to prevent accidental
calling our newly build tools.

Signed-off-by: Bart van der Meulen <bartvdrmeulen@gmail.com>

Fix MPFR build to recognise the Mingw32 case.

Once we have canadian in place, Mingw32 can be a legitimate host,
so we have to recognise that along with Cygwin.

Also fix recognising Cygwin hosts.

Signed-off-by: Bart van der Meulen <bartvdrmeulen@gmail.com>

Use configured shell in all build-tools wrappers

Abide by the user's wish to use dash as shell in
build-tools wrappers, instead of plain /bin/sh.