Cheesy kconfig stuff:
- silent/quiet/verbose build:
- ct-ng by default only prints quit messages, such as "CC xxx",
- if using V=0, nothing is printed,
- if using V=1, the full command lines are printed,
- other values are indeterminate,
- should help in debugging the kconfig stuff;
- complete kconfig/{,m}conf generation:
- fully dynamic dependencies on source files,
- compilation of .c into .o, then linking (instead of direct linking),
- VPATH usage when not --local;
Typo + a coment moved.

/trunk/kconfig/kconfig.mk | 140 87 53 0 +++++++++++++++++++++++++++++++++--------------------
/trunk/tools/tools.mk | 12 6 6 0 ++--
/trunk/steps.mk | 6 3 3 0 +-
/trunk/samples/samples.mk | 30 15 15 0 +++++-----
/trunk/ct-ng.in | 40 28 12 0 +++++++++++----
5 files changed, 139 insertions(+), 89 deletions(-)

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.