public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23602] [4.1 regression] 1081 test failures in libjava, when configured for i486-linux
Date: Wed, 31 Aug 2005 14:12:00 -0000	[thread overview]
Message-ID: <20050831140842.21173.qmail@sourceware.org> (raw)
In-Reply-To: <20050828164012.23602.debian-gcc@lists.debian.org>


------- Additional Comments From debian-gcc at lists dot debian dot org  2005-08-31 14:08 -------
tracked down the 1000+ test failures to the import of classpath from 20050716
(well not exactly, but between 2005-07-16 00:00 UTC and 02:00 UTC).

  Matthias

2005-07-15  Mark Mitchell  <mark@codesourcery.com>

       PR c++/22204
       * repo.c (repo_emit_p): Robustify.

2005-07-15  Tom Tromey  <tromey@redhat.com>

       Major merge with Classpath.
       Removed many duplicate files.
       * HACKING: Updated.x
       * classpath: Imported new directory.
       * standard.omit: New file.
       * Makefile.in, aclocal.m4, configure: Rebuilt.
       * sources.am: New file.
       * configure.ac: Run Classpath configure script.  Moved code around
       to support.  Disable xlib AWT peers (temporarily).
       * Makefile.am (SUBDIRS): Added 'classpath'
       (JAVAC): Removed.
       (AM_CPPFLAGS): Added more -I options.
       (BOOTCLASSPATH): Simplified.
       Completely redid how sources are built.
       Include sources.am.
       * include/Makefile.am (tool_include__HEADERS): Removed jni.h.
       * include/jni.h: Removed (in Classpath).
       * scripts/classes.pl: Updated to look at built classes.
       * scripts/makemake.tcl: New file.
       * testsuite/libjava.jni/jni.exp (gcj_jni_compile_c_to_so): Added
       -I options.
       (gcj_jni_invocation_compile_c_to_binary): Likewise.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23602


  parent reply	other threads:[~2005-08-31 14:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28 16:41 [Bug target/23602] New: " debian-gcc at lists dot debian dot org
2005-08-28 17:20 ` [Bug target/23602] " debian-gcc at lists dot debian dot org
2005-08-28 21:58 ` pinskia at gcc dot gnu dot org
2005-08-29 21:08 ` debian-gcc at lists dot debian dot org
2005-08-30  2:46 ` rth at gcc dot gnu dot org
2005-08-30  6:00 ` rth at gcc dot gnu dot org
2005-08-30  7:33 ` debian-gcc at lists dot debian dot org
2005-08-31 10:17 ` debian-gcc at lists dot debian dot org
2005-08-31 14:12 ` debian-gcc at lists dot debian dot org [this message]
2005-09-02 21:39 ` rth at gcc dot gnu dot org
2005-09-02 21:46 ` tromey at gcc dot gnu dot org
2005-09-02 22:09 ` rth at gcc dot gnu dot org
2005-09-02 22:21 ` debian-gcc at lists dot debian dot org
2005-09-05 13:26 ` debian-gcc at lists dot debian dot org
2005-09-26 13:23 ` debian-gcc at lists dot debian dot org
     [not found] <bug-23602-5724@http.gcc.gnu.org/bugzilla/>
2005-10-05 18:19 ` cvs-commit at gcc dot gnu dot org
2005-10-05 18:23 ` rth at gcc dot gnu dot org
2006-01-21  2:11 ` aoliva at gcc dot gnu dot org
2006-03-17  6:25 ` aoliva at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050831140842.21173.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).