The old READMEs

["Joseph S. Myers" <jsm28 at cam dot ac dot uk>]

The GCC 3.0 release criteria include unified installation documentation.  
In addition to the installation documentation listed there, some of the
READMEs in the gcc/ directory also have relevant information and should be
merged in.  Some may also be obsolete; information about problems with
obsolete systems that may not apply to current GCC should be clearly
separated from that relevant to vaguely current systems.

Summary of the files involved that could do with being unified with the
manual or install documentation or web pages:

PROBLEMS: Not changed since the start of EGCS.  Someone should check
whether anything there is still relevant and add it to GNATS or the
projects web pages if appropriate.  (An interim fix would simply be to
insert this file in projects.html as a list for interested people to check
and remove items from - but I doubt it's useful in the distribution.)

README-bugs: Not changed since the start of EGCS.  If anything is
relevant, it should go in the online bug reporting instructions.

README.ACORN, README.ALTOS, README.APOLLO, README.X11 (all obsolete? -
none changed since the start of EGCS apart from typo fixes in README.X11):
Belong in installation instructions or removed.

README.FRESCO (not changed since the start of EGCS): Obsolete?

README.AVR, README.C4X, README.NS32K, README.RS6000: Probably better in
the manual than as a README.

README.TRAD, TESTS.FLUNK (neither changed since the start of EGCS):
Probably better in the relevant sections of the manual.  I can produce a
patch to move these to the manual if it is felt appropriate to move the
contents of these files.

README.gnat: May need updating to relate to whatever version of GNAT is
released that works with GCC 3.0; without such a GNAT, will be irrelevant
and should be removed.

SERVICE: Probably better to reference the online GNU Service Directory
<URL:http://www.gnu.org/prep/service.html>.

-- 
Joseph S. Myers
jsm28@cam.ac.uk