From: "Andre Oliveira da Costa" <costa@cade.com.br>
To: <cygwin@sourceware.cygnus.com>
Subject: RE: bash, javac and that pesky slash.
Date: Mon, 24 Jan 2000 09:49:00 -0000 [thread overview]
Message-ID: <001401bf6693$4e1a10e0$8400000a@costa.cadenet.com.br> (raw)
In-Reply-To: <v04220802b4b23e518417@[206.173.234.247]>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
That's true. jdk is a Windows native application, it wasn't compiled with
cygwin. Therefore, it doesn't understand the '/' used by UNIX (cygwin); you
must use the M$ '\'. Also, drives must be referenced by their "names" (e.g.
"D:" in your case, and not "//d"). Other: the CLASSPATH environment variable
must use M$-path-style also, because it is meant to be interpreted by jdk
tools.
HTH.
Regards,
Andre
--
André Oliveira da Costa
(costa@cade.com.br)
> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Randall R Schulz
> Sent: Monday, January 24, 2000 3:39 PM
> To: Craig MacFarlane; cygwin@sourceware.cygnus.com
> Subject: Re: bash, javac and that pesky slash.
>
>
> 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.
--
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:49 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 [this message]
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='001401bf6693$4e1a10e0$8400000a@costa.cadenet.com.br' \
--to=costa@cade.com.br \
--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).