public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: ant fix for gcj
Date: Sun, 16 May 2004 05:07:00 -0000	[thread overview]
Message-ID: <1084684019.3631.70.camel@escape> (raw)

Gary,

I just filed a bug report and patch with the ant people:

http://issues.apache.org/bugzilla/show_bug.cgi?id=29020

This patch (against upstream ant cvs) adds the proper libgcj.jar file to
the bootclasspath when required (building with jikes, or ecj, etc).

Would it be ok to commit something similar to the rhug ant?

Index: src/main/org/apache/tools/ant/types/Path.java
===================================================================
RCS file: /home/cvspublic/ant/src/main/org/apache/tools/ant/types/Path.java,v
retrieving revision 1.62
diff -u -r1.62 Path.java
--- src/main/org/apache/tools/ant/types/Path.java	9 Mar 2004 16:48:41 -0000	1.62
+++ src/main/org/apache/tools/ant/types/Path.java	16 May 2004 04:54:59 -0000
@@ -587,7 +587,10 @@
             }
         }
 
-        if (System.getProperty("java.vendor").toLowerCase(Locale.US).indexOf("microsoft") >= 0) {
+	if ("GNU libgcj".equals(System.getProperty("java.vm.name"))) {
+	    addExisting(new Path(null,
+                                 System.getProperty("sun.boot.class.path")));
+        } else if (System.getProperty("java.vendor").toLowerCase(Locale.US).indexOf("microsoft") >= 0) {
             // Pull in *.zip from packages directory
             FileSet msZipFiles = new FileSet();
             msZipFiles.setDir(new File(System.getProperty("java.home")


AG

-- 
Anthony Green <green@redhat.com>
Red Hat, Inc.

                 reply	other threads:[~2004-05-16  5:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1084684019.3631.70.camel@escape \
    --to=green@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=rhug-rhats@sources.redhat.com \
    /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).