diff options
author | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
---|---|---|
committer | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
commit | 554fd8c5195424bdbcabf5de30fdc183aba391bd (patch) | |
tree | 976dc5ab7fddf506dadce60ae936f43f58787092 /libjava/mauve-libgcj | |
download | cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.bz2 cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.xz |
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.
downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.
if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.
Diffstat (limited to 'libjava/mauve-libgcj')
-rw-r--r-- | libjava/mauve-libgcj | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/libjava/mauve-libgcj b/libjava/mauve-libgcj new file mode 100644 index 000000000..4d4cf5bc1 --- /dev/null +++ b/libjava/mauve-libgcj @@ -0,0 +1,25 @@ +# Config file that tells mauve about the `libgcj' tag. +JDK1.0 +JDK1.1 +JDK1.2 +JDK1.3 +JDK1.4 +JLS1.0 +JLS1.1 +JLS1.2 +JDBC1.0 +JDBC2.0 + +# The following tests seem to hang or crash the testsuite. +# This a problem when running Mauve "standalone". +!java.lang.reflect.Array.newInstance + +# These are almost certainly buggy test cases. +# The behaviour of the garbarge collector cannot be predicted. +# Note the . at the end so we do test java.lang.reflect +!java.lang.ref. + +# Tests for not yet implemented classes and/or methods. +!java.awt.event.MouseEvent.modifiersEx +!org.omg. +!javax.rmi |