This is the mail archive of the
mailing list for the Cygwin project.
Re: Compiled Program System Calls Failing Code 127
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 17 May 2011 12:11:46 -0400
- Subject: Re: Compiled Program System Calls Failing Code 127
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On 5/16/2011 4:07 PM, Leon Vanderploeg wrote:
I have a compiled C program that is installed on several servers. It makes
system calls to programs such as rsync, and has worked fine until now. I
recently installed it on two Server 2008R2 boxes, identical hardware. Both
are Cygwin 1.7.9. C:\cygwin\bin is added to the Windows PATH variable on
both machines. The program runs fine on one box, but on the other box, the
system calls return 127.
http://cygwin.com/ml/cygwin/2006-08/msg00347.html says /bin/sh can’t be
found. At the escalated command prompt, bash and sh start appropriate
shells (although the which command points to /usr/bin/xxx) on both machines.
Any idea what could be causing this behavior?
No, not really. But I'd say it would be worth a look to see how the two
environments differ, including permissions. cygcheck output from the two
machines might help you understand at least some of this. If not, you may
have to do some debugging of the code on both machines to find the problem.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple