Mail Archives: cygwin/1997/01/02/17:24:58
At 03:54 PM 1/2/97 -0500, you wrote:
>The mount mechanism doesn't seem to work properly with Microsoft's
>compiler, cl.exe. Inside bash (17.1 release), the c: drive is mounted
>as /. The following works:
>
> bash$ ls -l /foo/bar.c
> -rw-r--r-- 1 500 everyone 795 Jan 02 15:44 /foo/bar.c
>
> bash$ cl /c c:/foo/bar.c
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 10.20.6166 for 80x86
> Copyright (C) Microsoft Corp 1984-1996. All rights reserved.
>
> bar.c
>
>But if I try to do:
>
> bash$ cl /c /foo/bar.c
>
>the compiler barfs with:
>
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 10.20.6166 for 80x86
> Copyright (C) Microsoft Corp 1984-1996. All rights reserved.
>
> Command line warning D4002 : ignoring unknown option '/foo/bar'
> Command line error D2003 : missing source filename
>
>Apparently, cl.exe is making some assumptions about its command line
>arguments that aren't accounted for in cygwin.dll's path tranlation
>scheme? I suspect other MS apps may suffer the same problem...
In DOS (NT command prompt) the option introduction character is defaulted
to '/' as apposed to Unix's '-'. cl is reading the /f as a compiler
option. This has nothing to do with bash and can't even be addressed
by bash. You'd have the same problem in unix if you had a file whose
name started with a hyphen. It'd be best in this case if you just
used the backslashes.
--blake
--
Get info on my Dynace Object Oriented Extension to C
and Windows Development System from:
http://www.edge.net/algorithms
Blake McBride (blake AT edge DOT net)
Algorithms Corporation - 615-791-1636 - USA
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -