From: Chris Faylor <cygwin@sourceware.cygnus.com>
To: Craig MacFarlane <craigm@chemconnect.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: bash, javac and that pesky slash.
Date: Mon, 24 Jan 2000 09:41:00 -0000 [thread overview]
Message-ID: <20000124125539.A21469@cygnus.com> (raw)
In-Reply-To: <388C8C72.8BB82F3E@chemconnect.com>
On Mon, Jan 24, 2000 at 09:31:30AM -0800, Craig MacFarlane wrote:
>Sun's javac, in jdk1.2.1, seems to change the forward slashes used by
>bash to backward slashes used by windows.
>
>e.g.
>
>bash-2.02% javac -d //d/destdir/classes foo.java
>
>produces the error message
>
>The \\d\destdir\classes directory does not exist.
>
>Is there any way to use javac with bash while specifying destination
>dirs for your classes? It appears as though javac is trying to be too
>smart by substituting slashes.
Is there some reason why you're asking this question here rather than
in, say a Sun javac mailing list?
FYI, even if you could do something magical to javac to cause it
to emit forward slashes, it still would not understand the //d
drive syntax since this is cygwin specific. For an application
to understand cygwin drive specs, it would need to be linked with
the cygwin DLL.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-01-24 9:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-24 9:32 Craig MacFarlane
2000-01-24 9:39 ` Randall R Schulz
2000-01-24 9:41 ` Chris Faylor
2000-01-24 9:55 ` Randall R Schulz
2000-01-24 9:49 ` Andre Oliveira da Costa
2000-01-24 9:41 ` Chris Faylor [this message]
2000-01-24 11:36 ` Kazuhiro Fujieda
2000-01-24 11:03 David Robinow
2000-01-24 11:53 ` Andre Oliveira da Costa
2000-01-24 12:40 Halim, Salman
2000-01-24 16:05 Paul Johnston
2000-01-24 18:17 Eric Feliu
2000-01-25 9:20 ` Jeff Sturm
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=20000124125539.A21469@cygnus.com \
--to=cygwin@sourceware.cygnus.com \
--cc=craigm@chemconnect.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).