This is the mail archive of the
mailing list for the Cygwin project.
RE: Signal 127 when doing make
- From: "Manik, Raina (IE10)" <Manik dot Raina at honeywell dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 15 Jun 2003 19:47:25 -0700
- Subject: RE: Signal 127 when doing make
~> Signal 127 usually means that some application could not
~> be exec'd. Look
~> at the make output before that point. Try getting make
~> to echo your
~> commands (by running it with -n, for example) and check
~> that all the
~> necessary programs exist and are executable. Check your
~> shell settings,
~> check the make mode (try explicitly passing --unix to make).
It seems to exec just fine, because the same command with different
command line arguments exec'ed later works fine. I was wondering if
it could have something to do with the return value of the application.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html