Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: Bizarre behaviour of "make --win32" Date: Tue, 14 Sep 2004 16:01:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-ID: X-OriginalArrivalTime: 14 Sep 2004 15:01:38.0359 (UTC) FILETIME=[BC3E3C70:01C49A6B] Afternoon folks, When I use make with the "--win32" flag, it is supposed to use cmd.exe rather than sh.exe to spawn the command lines that are used to build a target, isn't it? For some strange reason, however, its behaviour varies according to whether or not the command line includes stdout redirection. It appears to be using sh.exe, regardless of the --win32 flag. But if I add stdout redirection to the command in question, it uses cmd.exe. As it happens, in my particular setup this then causes it to fail in a fairly amusing fashion with ntvdm trying to execute what are very clearly ascii chars rather than opcodes, because cmd isn't able to follow a cygwin symlink, but that's a side issue. The point is that I want to get consistent behaviour. So, a couple of quick questions, just to confirm I'm not barking up a tree other than the right one: 1) Is this the right place for discussing the --win32 flag? It doesn't seem to exist in the upstream gnu sources, so I was wondering if it's a cygwin speciality, or if I should take it up with mingw? 2) Is this behaviour known / intended / understood? 3) Would anyone like to see my (very) minimal testcase? cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/