public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Randall R Schulz <rschulz@teknowledge.com>
To: Craig MacFarlane <craigm@chemconnect.com>, cygwin@sourceware.cygnus.com
Subject: Re: bash, javac and that pesky slash.
Date: Mon, 24 Jan 2000 09:39:00 -0000	[thread overview]
Message-ID: <v04220802b4b23e518417@[206.173.234.247]> (raw)
In-Reply-To: <388C8C72.8BB82F3E@chemconnect.com>

Craig,

You must distinguish Cygwin programs from all others and use Windows 
native path name syntax for any program not compiled for Cygwin. For 
me, this most often manifests itself when I wish to launch Vim.

Randy Schulz
Teknowledge Corp.
Palo Alto, CA USA


At 09:31 -0800 1/24/00, 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.
>
>Thanks,
>Craig



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-01-24  9:39 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 [this message]
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
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='v04220802b4b23e518417@[206.173.234.247]' \
    --to=rschulz@teknowledge.com \
    --cc=craigm@chemconnect.com \
    --cc=cygwin@sourceware.cygnus.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).