This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
libgcj/2874: libjava testsuite disk space usage
- To: gcc-gnats at gcc dot gnu dot org
- Subject: libgcj/2874: libjava testsuite disk space usage
- From: Joseph Myers <jsm28 at cam dot ac dot uk>
- Date: Sat, 19 May 2001 18:49:54 +0000
- Cc: jsm28 at cam dot ac dot uk
>Number: 2874
>Category: libgcj
>Synopsis: libjava testsuite disk space usage
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat May 19 11:56:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.1 20010519 (experimental)
>Organization:
none
>Environment:
System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/mainline --disable-shared --enable-threads=posix --with-system-zlib
>Description:
The libjava testsuite leaves executables from successful tests around
in builddir/i686-pc-linux-gnu/libjava/testsuite/. With
--disable-shared, these take up about 700Mb, more than the total disk
space used by the rest of building GCC.
The practice used by the gcc testsuite is only to leave around
executables from failed tests; I think the libjava one should do the
same.
>How-To-Repeat:
Bootstrap and test with --disable-shared.
>Fix:
Arrange for the libjava testsuite only to leave executables around for
failed tests, and to delete them (and .o/.lo/.class files) for tests
that succeed.
>Release-Note:
>Audit-Trail:
>Unformatted: