--- David Starks-Browning <[EMAIL PROTECTED]> wrote:
> The FAQ now says:
>
> Q. Why is make behaving badly?
>
> A. Make has two operating modes, UNIX and WIN32. You need to make
> sure that you are operating in the right mode.
>
> In UNIX mode, make uses sh.exe as a subshell. The path list
> separator is ':', '\' is the escape character, POSIX paths are
> expected, and Cygwin mounts will be understood. Use this for
> Makefiles written for UNIX.
>
> In WIN32 mode, make uses the "native" command shell (cmd.exe
> or command.com), with all the restrictions that implies. The
> path list separator is ';', the path separator is '\', "copy"
> and "del" work, but the Cygwin mount table is not
> understood. Use this for nmake-style Makefiles.
>
> The default mode for the Net Release of make (the one
> installed by setup.exe) is UNIX. The default mode for
> commercial releases to Redhat (formerly Cygnus) customers is
> WIN32.
>
> You can override the default by setting the environment
> variable MAKE_MODE to "UNIX" (actually case is not
> significant) or "WIN32" (actually anything other than
> "UNIX"). You can also specify the options --unix or --win32 on
> the make command line.
>
> Is this an accurate explanation?
>
Excellent. Written so that anyone who can understand English can understand
what happens with the two modes. Nice job.
Cheers,
=====
Earnie Boyd
mailto:[EMAIL PROTECTED]
--- <http://earniesystems.safeshopper.com> ---
--- Cygwin: POSIX on Windows <http://gw32.freeyellow.com/> ---
--- Minimalist GNU for Windows <http://www.mingw.org/> ---
__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf! It's FREE.
http://im.yahoo.com/
--
Want to unsubscribe from this list?
Send a message to [EMAIL PROTECTED]
