public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "fitzsim at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/27890] [4.2 regression] lib/logging.properties pollutes common namespace
Date: Tue, 06 Jun 2006 14:07:00 -0000	[thread overview]
Message-ID: <20060606140746.18551.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27890-231@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from fitzsim at redhat dot com  2006-06-06 14:07 -------
On the JDK lib files are stored in $JAVA_HOME/jre/lib.  I've recently moved
some files, like libjawt.so, that would conflict for multiple, parallel libgcj
installations to the same prefix, to $(libdir)/gcj-$(gcc_version).  I think we
should move all such files there, and that directory should be libgcj's
equivalent to the JDK's $JAVA_HOME/jre/lib.


-- 


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


  parent reply	other threads:[~2006-06-06 14:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04 11:09 [Bug libgcj/27890] New: " gerald at pfeifer dot com
2006-06-04 11:15 ` [Bug libgcj/27890] " gerald at pfeifer dot com
2006-06-04 11:17 ` rguenth at gcc dot gnu dot org
2006-06-04 19:31 ` jsm28 at gcc dot gnu dot org
2006-06-04 20:02 ` mmitchel at gcc dot gnu dot org
2006-06-05 20:06 ` tromey at gcc dot gnu dot org
2006-06-05 20:50 ` rguenth at gcc dot gnu dot org
2006-06-06 14:07 ` fitzsim at redhat dot com [this message]
2006-06-06 21:04 ` gerald at pfeifer dot com
2006-08-14  0:01 ` debian-gcc at lists dot debian dot org
2006-08-14 19:41 ` fitzsim at redhat dot com
2006-08-15 16:05 ` tromey at gcc dot gnu dot org
2006-08-21 22:19 ` tromey at gcc dot gnu dot org
2006-08-22 18:03 ` david at jpackage dot org
2006-08-22 20:37 ` fitzsim at gcc dot gnu dot org
2006-08-22 20:41 ` 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=20060606140746.18551.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).