Subject: NOTE: gcc 2.95 import soon
To: None <tech-toolchain@netbsd.org>
From: Todd Vierling <tv@pobox.com>
List: tech-toolchain
Date: 07/04/2000 20:19:42
If you're subscribed to source-changes, you'll see an import of gcc 2.95.2
on Friday into src/gnu/gcc-2.95/dist.  There are some points to note about
this import, which are listed here to solicit objections or modifications:

- gcc 2.9x will not be part of 1.5.x.  This is intentional, because gcc
  2.9x still has many known issues [bugs] on several architectures that
  will need to be worked out before a release.  I will not entertain
  discussion about forklifting it into 1.5, but I will make a pkg available,
  once integration is completed, for pre-1.6 systems to use the compiler.

- This is not being imported into gnu/dist because the top-level
  configuration between gcc and other tools (binutils, etc.) is slowly
  diverging.  Though it's possible to build binutils and gcc from the same
  tree, it's no longer a regularly tested practice, so the import will focus
  on keeping the `dist' tree as close as possible to the gcc distribution.

- This is being imported to a version-specific subdirectory based on the
  established history of integration of a new compiler into NetBSD.  
  Typically architectures need to move gradually to the new system where a
  non-point release update of the compiler is concerned, so we will need
  another gradual move for each of gcc 2.96 and gcc 3.0.

- The testsuites and other (non-NetBSD) architectures are being imported, to
  keep the `dist' tree close to the real thing.  I will be making `make
  test' targets to make use of the testsuites.

- All of the autoconf-based configuration scripts will be available, to
  allow for direct creation of a cross-compile environment.

- libcc1.so will probably resurface for some ports (or as an option), but be
  much slimmer, as the common compiler portions have changed a bit since
  egcs 1.1.  I will also be moving libcc1, and the (now eight) cc1 and
  related programs, to a subdirectory, /usr/libexec/gcc, to keep them well
  grouped.

If you have questions about this integration (besides "when will it be
done?"), or suggestions to modify the plan, please mail me in private.

-- 
-- Todd Vierling (tv@pobox.com)