Ah! I finally have a progress bar that doesn't stall the build!
- pipe size in Linux is only 8*512=4096 bytes
- pipe size is not setable
- when the feeding process spits out data faster than the eating
process can read it, then the feeding process stalls after 4KiB
of data sent to the pipe
- for us, the progress bar would spawn a sub-shell every line,
and the sub-shell would in turn spawn a 'date' command.
Which was sloooww as hell, and would cause some kind of a
starvation: the pipe was full most of the time, and the
feeding process was stalled all this time.

Now, we use internal variables and a little hack based onan offset
to determine the elapsed time. Much faster this way, but still
CPU-intensive.

 --- gcc/gcc/config.gcc.uclibc100-sh~	2006-03-06 20:46:56 +0100

 +++ gcc/gcc/config.gcc	2006-03-10 15:02:41 +0100

 @@ -1905,7 +1905,7 @@

  	;;

  sh-*-elf* | sh[12346l]*-*-elf* | sh*-*-kaos* | \

  sh-*-symbianelf* | sh[12346l]*-*-symbianelf* | \

 -  sh-*-linux* | sh[346lbe]*-*-linux* | \

 +  sh*-*-linux* | sh[346lbe]*-*-linux* | \

    sh-*-netbsdelf* | shl*-*-netbsdelf* | sh5-*-netbsd* | sh5l*-*-netbsd* | \

     sh64-*-netbsd* | sh64l*-*-netbsd*)

  	tmake_file="${tmake_file} sh/t-sh sh/t-elf"