Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <394550B8.905A1B35@carlthompson.net> Date: Mon, 12 Jun 2000 14:06:00 -0700 From: Carl Thompson X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.14-5.0 i686) MIME-Version: 1.0 To: Paul Kinnucan Cc: Cygwin List Subject: Re: Make and javac compliler problem in bash References: <4 DOT 1 DOT 20000612123820 DOT 01ed6a10 AT pop DOT mathworks DOT com> <4 DOT 1 DOT 20000612154844 DOT 01ed33d0 AT pop DOT mathworks DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Paul Kinnucan wrote: > ... > >> How could it be otherwise? The Windows version of javac is, > >> surprise, a Windows application. Windows applications don't > >> recognize Unix paths. Ergo, the Windows version of javac does not > >> recognize Unix paths. QED. > > > >Actually, Win32 _does_ allow path names to use forward slashes as the > >directory separator. The FAQ question you pointed out above even > >mentions > > But not to BEGIN a path as in Jin's example. That's certainly not what you wrote above, is it? Nor is it true. There is nothing inherent in Win32 that says it can't use paths that begin with a "/" . Try pulling up a command prompt and type notepad /path/to/a/file This works on my system (Windows 2000). Some programs are written in such a way that they can handle forward slashes in paths. "command.com" and "cmd.exe" have some problems dealing with them, and it looks like "javac" does too. This is _not_ a limitation in Windows as you assert, but a limitation of this programs. > - Paul Carl Thompson -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com