Introduce the notion of a 'sample comment'.

- presence of the sample's reported.by file is now mandatory.
- when saving a sample, reporter name & URL are queried, to avoid operator forget about creating the reported.by file.
- when saving a sample, one can store a few-liner comment.
- when recalling a sample, the reporter name, URL and comment (if present) are printed.
- update the powerpc-e500v2-linux-gnuspe sample to include Nate's comment (from his original mail).
- update all samples that were missing the reported.by file.

/trunk/scripts/saveSample.sh | 46 35 11 0 ++++++++++++++++++------
/trunk/scripts/showSamples.sh | 12 6 6 0 +++---
/trunk/samples/powerpc-e500v2-linux-gnuspe/reported.by | 15 15 0 0 ++++++++
/trunk/samples/samples.mk | 22 17 5 0 +++++++++--
4 files changed, 73 insertions(+), 22 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.