public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/20750] libgcj needs a --with-java-home configure option Date: Mon, 04 Apr 2005 21:27:00 -0000 [thread overview] Message-ID: <20050404212731.13373.qmail@sourceware.org> (raw) In-Reply-To: <20050404191026.20750.fitzsim@redhat.com> ------- Additional Comments From mckinlay at redhat dot com 2005-04-04 21:27 ------- Yeah, in the case where java-gcj-compat is merged into libgcj (ie libgcj is set up to look like a JVM) then this option makes sense. libgcj would install its .jars and whatever other JVMish files applications expect to find into this directory, and set java.home accordingly. I don't see a reason why we couldn't go ahead and implement this on HEAD now, even though an external wrapper would still be needed for now to use ecj as javac. I so think it seems a bit non-intuitive to have --with-java-home just set a property and not actually install things into that directory, relying on an external package to actually populate it, however. We should at least install libgcj.jar into the directory given? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20750
next prev parent reply other threads:[~2005-04-04 21:27 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-04 19:10 [Bug java/20750] New: " fitzsim at redhat dot com 2005-04-04 19:11 ` [Bug libgcj/20750] " fitzsim at redhat dot com 2005-04-04 19:15 ` pinskia at gcc dot gnu dot org 2005-04-04 20:03 ` mckinlay at redhat dot com 2005-04-04 20:44 ` fitzsim at redhat dot com 2005-04-04 20:48 ` fitzsim at redhat dot com 2005-04-04 21:27 ` mckinlay at redhat dot com [this message] 2005-04-04 21:39 ` fitzsim at redhat dot com 2005-04-05 23:46 ` cvs-commit at gcc dot gnu dot org 2005-04-06 3:44 ` cvs-commit at gcc dot gnu dot org 2005-04-06 3:57 ` fitzsim at redhat dot com 2005-04-06 6:55 ` pinskia 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=20050404212731.13373.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: linkBe 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).