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.

http://mirror.sh-linux.org/rpm-2003/SRPMS/gcc-3.2.3-3.src.rpm contains the following patches:

gcc-20030210-sh-linux-1.patch

gcc-3.2.3-libffi-1.patch

gcc-3.2.3-sh-linux-dwarf2-1.patch (*not* applied by the spec file, it's in there by accident)

gcc-3.2.3-libffi-1.patch was needed just to build, I think.

After that was applied, sh4 gcc seemed to compile fine, but c++ programs

failed to execute because libstdc++.so.5 was built without version

info.  This was caused directly by libstdc++-v3/configure setting

SYMVER_MAP=config/linker-map.dummy because it sees that 

no libgcc_s.so was generated; configure says

  checking for shared libgcc... no.

Applying gcc-20030210-sh-linux-1.patch in hopes it makes those problems go away.