Huge fixes to glibc build, so that we can build at least (and at last):
- use ports addon even when installing headers,
- use optimisation (-O) when installing headers, to avoid unnecessary warnings (thanks Robert P. J. DAY for pointing this out!),
- lowest kernel version to use is only X.Y.Z, not X.Y.Z.T,
- a bit of preparations for NPTL (RSN I hope),
- fix fixing the linker scripts (changing the backup file is kind of useless and stupid);

Shut uClibc finish step: there really is nothing to do;

Add a patch for glibc-2.3.6 weak aliases handling on some archs (ARM and ALPHA at least);

Did not catch the make errors: fixed the pattern matching in scripts/functions;

Introduce a new log level, ALL:
- send components' build messages there,
- DEBUG log level is destined only for crosstool-NG debug messages,
- migrate sub-actions to use appropriate log levels;

Update the armeb-unknown-linux-gnu sample:
- it builds!
- uses gcc-4.0.4 and glibc-2.3.6,
- updated to latest config options set.

 When configuring canadian cross toolchain and you're unlucky enough to be

 using a build and host that are different, but that config.sub thinks mean the same thing,

 you might end up without BUILD_CC being defined as 'cc' or 'gcc',

 which might cause $CC to be used instead, which would be wrong...

 Dan Kegel

 --- glibc-2.3.2/configure.old	2004-05-26 19:46:43.000000000 -0700

 +++ glibc-2.3.2/configure	2004-05-26 19:52:47.000000000 -0700

 @@ -3323,7 +3323,7 @@

  ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'

  ac_compiler_gnu=$ac_cv_c_compiler_gnu

 -if test $host != $build; then

 +if test "$cross_compiling" = yes; then

    for ac_prog in gcc cc

  do

    # Extract the first word of "$ac_prog", so it can be a program name with args.