This is the mail archive of the
mailing list for the Cygwin project.
Re: Different behaviour of "test -f" under cmd and bash, when calledfrom compiled App
- From: Brian Ford <ford at vss dot fsi dot com>
- To: Luis Torres <torres2003 at sapo dot pt>
- Cc: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Tue, 9 Dec 2003 16:40:24 -0600 (CST)
- Subject: Re: Different behaviour of "test -f" under cmd and bash, when calledfrom compiled App
- References: <200312092230.hB9MUerM015044@mailgw01.flightsafety.com>
On Tue, 9 Dec 2003, Luis Torres wrote:
> 2) In relation to the above I tracked the following problem. If I use (interactive shell):
> test -f AfileIKnowExists && echo YES (under either cmd.exe or Cygwin/bash), I get the correct answer
> (test.exe from /cygdrive/c/cygwin/bin as per official distribution)
> while if I use the code bellow within a program.exe compiled under Cygwin, I get the correct answer if
> I use it within bash but NOT the correct answer if I use the program in cmd.exe
> Code : "
> strcpy(command,"test -f ");
> fprintf(stderr,"Executing %s\n", command);
I don't see the problem right off, but HTH.
This will do:
/bin/sh -c command
Also, sh is ash.
With a command argument, the result of `system' is the exit
status returned by `/bin/sh'.
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html