This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Make and VC++ compiler problems
- To: camip at sol dot dk
- Subject: Re: Make and VC++ compiler problems
- From: Peter Buckley <peter dot buckley at cportcorp dot com>
- Date: Sat, 15 Sep 2001 14:18:47 -0400
- CC: cygwin at cygwin dot com
- References: <3B8AE3790002CAB1@cpmail.asap.asp.net>
I think your problem is that Cygwin's make uses /bin/sh.exe
as its default shell, in its default MAKE_MODE, which is "unix".
If you open up a sh.exe shell, or a bash shell for that matter (IIRC),
and type "copy" you will get a "command not found" error.
You might be better off doing what Chris Faylor says, and using
nmake. Not that he is discouraging your use of cygwin, but
cygwin walks a fine line between POSIX and microsoft compatibility,
when microsoft is doing their best to avoid any POSIX behavior.
You can try setting MAKE_MODE=win32 in your environment, that will
use the Windows command shell, which will recognize the copy command.
IIRC there is no copy.exe because copy is a shell built in for
windows.
Hope that helps,
Peter
camip@sol.dk wrote:
>
> Hi,
>
> I'm trying to compile a library using make and the Visual C++ compiler.
>
> It's starting fine, but then it gives me this error: make[2]: copy: Command
> not found.
>
> It's strange because it should know the copy command. I can't find any copy.exe
> anywhere. Could that be a problem?.
>
> I'm compiling on platform win98.
>
> Hope you can help me.
>
> Camilla
>
> ________________________________________
> Få din egen webmail på http://mail.sol.dk - gratis og med dig overalt!
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/