public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "aaronavay62 at aaronwl dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/18104] Incorrect CLASSPATH separator in libjava breaks bootstrap
Date: Tue, 02 Nov 2004 22:32:00 -0000	[thread overview]
Message-ID: <20041102223202.5652.qmail@sourceware.org> (raw)
In-Reply-To: <20041022030156.18104.aaronavay62@aaronwl.com>


------- Additional Comments From aaronavay62 at aaronwl dot com  2004-11-02 22:31 -------
I agree with you with regards to the ugliness.

The entire situation is really too bad; the mutually incompatible path
separators used by Unix and Windows is definitely one of the top ten
compatibility problems in build systems.

GCJ definitely needs to accept ; on Windows, as whats what javac does.  I think
it would also be excellent if it accepted :, but I don't know the whole story
behind this.  In particular, I think there was some sort of code that could
handle nontrivial Windows path separator parsing, somewhere in GCC, but it was
removed, or something.  I really don't know enough about the issue to fix it myself.

Maybe there is some other way to fix this in the Makefiles, to make it so it
isn't so ugly?  Should a bug be opened for "CLASSPATH_SEPARATOR in Makefiles is
ugly"?


-- 


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


      parent reply	other threads:[~2004-11-02 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22  3:01 [Bug java/18104] New: " aaronavay62 at aaronwl dot com
2004-10-22  3:03 ` [Bug java/18104] " aaronavay62 at aaronwl dot com
2004-10-22  5:18 ` aaronavay62 at aaronwl dot com
2004-10-22 11:41 ` [Bug libgcj/18104] " pinskia at gcc dot gnu dot org
2004-10-27  2:43 ` cvs-commit at gcc dot gnu dot org
2004-10-27  2:46 ` pinskia at gcc dot gnu dot org
2004-11-02 16:11 ` mckinlay at redhat dot com
2004-11-02 22:32 ` aaronavay62 at aaronwl dot com [this message]

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=20041102223202.5652.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).