public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Java Discuss List <java@gcc.gnu.org>
Subject: Out of town
Date: Tue, 02 Apr 2002 20:38:00 -0000	[thread overview]
Message-ID: <87r8lxv5u9.fsf@creche.redhat.com> (raw)

Unfortunately I'm going out of town tomorrow and I'll be gone through
the end of the week.  This is rotten timing for the 3.1 release, but
it is unavoidable.  I probably won't have email connectivity.

I'd like to ask the other gcj hackers to respond to 3.1-related
problems for the next few days.

Some current status:

* The release-critical java/libgcj PRs all have high priority.

  * Gerald should be submitting a couple more Solaris problems to
    Gnats soon
  * There is a patch pending for PR 6068 and I have a partial patch
    for the last part of 5303 here (don't let that stop you from just
    doing it though :-).
  * AFAIK nobody is looking at 6066 yet.

* Darwin needs help; all the info I have is on the list

* There are actually 3 Solaris problems:
  * The configure change we need, so that we can warn if libgcj is
    already installed
  * The libffi configure bug
  * The -m64 exec. test failures

* Mark is doing a lot of Mauve work so expediting whatever he does
  will be helpful


I ought to put this info into the 3.1 status page but I probably won't
have time :-(.


Other folks, if you know of critical bugs or if your platform is
having problems (or if your platform should have libgcj enabled by
default but doesn't) then please send email to the list.  I'll try to
catch up on everything on Sunday.

Tom

             reply	other threads:[~2002-04-03  3:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 20:38 Tom Tromey [this message]
2002-04-03 14:53 ` Anthony Green

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=87r8lxv5u9.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=java@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).