public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug SWING/16776] JH will not build to a shared libary without some SWING classes
Date: Tue, 27 Jul 2004 02:53:00 -0000	[thread overview]
Message-ID: <20040727025313.15935.qmail@sourceware.org> (raw)
In-Reply-To: <20040727021858.16776.mwteng@hotmail.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-07-27 02:53 -------
No workaround at this point.  Basically if you want to work on these SWING classes as long as you have 
the nessary paper work, you welcomed to but it sounds like these classes are very low on the list.

-- 


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


  parent reply	other threads:[~2004-07-27  2:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27  2:19 [Bug java/16776] New: dependencies problem when converting jar to shared library mwteng at hotmail dot com
2004-07-27  2:26 ` [Bug java/16776] " pinskia at gcc dot gnu dot org
2004-07-27  2:36 ` mwteng at hotmail dot com
2004-07-27  2:38 ` [Bug SWING/16776] " pinskia at gcc dot gnu dot org
2004-07-27  2:40 ` [Bug SWING/16776] JH will not build to a shared libary without some SWING classes pinskia at gcc dot gnu dot org
2004-07-27  2:40 ` pinskia at gcc dot gnu dot org
2004-07-27  2:43 ` [Bug SWING/16776] dependencies problem when converting jar to shared library mwteng at hotmail dot com
2004-07-27  2:44 ` [Bug SWING/16776] JH will not build to a shared libary without some SWING classes pinskia at gcc dot gnu dot org
2004-07-27  2:44 ` pinskia at gcc dot gnu dot org
2004-07-27  2:48 ` mwteng at hotmail dot com
2004-07-27  2:53 ` pinskia at gcc dot gnu dot org [this message]
2005-08-21 16:08 ` [Bug swing/16776] " fitzsim at redhat dot com

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=20040727025313.15935.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).