Producing libgcj-2.95

[Warren Levy <warrenl@cygnus.com>]

Folks,
We're in the process of putting together a libgcj-2.95 distribution
to complement the gcc-2.95 distribution (which contains gcj).

As part of making this distribution, we'd like to understand on what 
platforms libgcj has been successfully built and tested.  A new cvs branch,

	libgcj-2_95-branch

has been created; after you have downloaded the source from this branch, 
built and tested it, please let us know how it went by sending your 
results to java-discuss@sourceware.cygnus.com in the following format:

e.g.

Platform		Configuration		Build 	Test Results
						Status
----------------------------------------------------------------------------
sparc-sun-solaris2.6	--enable-threads=posix	OK	x expected passes
			--enable-fast-character		y unexpected failures
							z expected failures


A list of deviations from the posted baseline list of test results should
follow the entry.  A context diff is fine if it is clear what tests are
failing; we'd rather not have to deal with a complete output listing unless
it is necessary to comprehend the deviations.

(For those downloading the libgcj source via snapshots rather than via
cvs, the snapshoting process has been temporarily changed to use the
libgcj-2_95-branch rather than the main trunk.  Please be aware of this
if you are looking for patches that get applied to the main source tree
but not to the branch).

Platform porting status and current current notes are posted at:

	<http://sourceware.cygnus.com/libgcj-platforms.html>.


Please note that there are important fixes added to the gcc-2.95 branch 
on 2-Jun-99 that are required in order to build the latest libgcj 
snapshot.  Please do a cvs update of your gcc-2.95 source if you do not 
already have these changes.  If you are getting source from snapshots rather 
than via cvs, a new gcc-2.95 snapshot and patch has been put together with
these fixes.

Another patch affecting gcj was made on 24-Jun-99.  Please do a cvs update
to obtain this patch.  The next snapshot with this patch will not be
available until 30-June-99.  In the meantime, those without cvs access
should consult the libgcj-platforms webpage mentioned at the bottom
of this mail for a possible workaround.


Baseline test results for comparison against the libjava.sum file 
created by running 'make check' in the libjava/testsuite dir of the 
build tree can be found at:

	<http://sourceware.cygnus.com/libgcj-sum.txt>

Please compare against these results and let us know of any deviations.
Note that if you are not using POSIX threads, some tests will not complete
successfully, so differences should be expected.

Be aware that the testsuites rely on the dejagnu package.  You can download
the current dejagnu snapshot from:

	<ftp://egcs.cygnus.com/pub/egcs/infrastructure/dejagnu-19990614.tar.gz>

Please note that some earlier versions of dejagnu are missing a patch
that's in recent snapshots.  Please make sure you have tried running
the testsuites with the current snapshot of dejagnu before reporting
any testsuite platform problems.  There is a short entry in the egcs FAQ
	<http://egcs.cygnus.com/faq.html#dejagnu>
if you would like more information about this issue.

In order to more fully exercise libgcj, it is highly recommended to  
include the Mauve testsuite in the test run.  The Mauve tests are
available for download from:
 
	<http://sourceware.cygnus.com/mauve/download.html>

Also note the Mauve tests require the following configuration prior to
running 'make check':

- The env variable MAUVEDIR must be set to the top of the Mauve source tree
- By default, tests that first compile to bytecode use an installed 'javac'
  program.  Set the environment variable JAVAC to 'gcj -C' to use the
  installed gcj for this purpose.


It is highly recommended that you not override the default libgcj 
configuration for building with dynamic libraries.  This is to avoid
having to explicitly specify some libgcj object modules on the link line 
to get certain java/net Mauve tests to execute.


Please note that a new mailing list, java-patches@sourceware.cygnus.com
has been created for patch submissions. We plan to use this list just as
egcs uses the egcs-patches list: all patches will be sent to the list.
If you have a patch you want considered, please send it there along with
an explanation and a ChangeLog entry. 

Developers with checkin-after-approval access should also send patches
to this list, and then check them in after approval is given.  Developers
with direct checkin access should also send patches to this list; this
can happen concurrently with the checkin. 

Some discussion will probably take place on this list (just as with
egcs-patches). The web page has subscription info, as well as a link
to the archives. 

The java-patches mailing list is for patches to the libgcj code
(libjava, boehm-gc, zlib, etc) code only. In particular, compiler
patches still have to go through egcs, so please don't send them
to java-patches. 

Finally, please be aware that libgcj-2.95 should be considered frozen
except for low-risk porting changes that increase coverage to new
target platforms (i.e. those changes that would not affect other
platforms).  High priority changes will be determined and considered
on a case by case basis.  All other changes will only go into the main
trunk and not the libgcj-2_95-branch. 


Thanks in advance for your help on the libgcj project!
--warrenl

-----------
Warren Levy
Cygnus Solutions, Sunnyvale, CA  USA