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 Message-ID: <77ED2BF75D59D1439F90412CC5B109740263@ie10-sahara.hiso.honeywell.com> From: "Manik, Raina (IE10)" To: cygwin AT cygwin DOT com Subject: RE: Signal 127 when doing make Date: Sun, 15 Jun 2003 19:47:25 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" ~> ~> Manik, ~> ~> 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). ~> Igor 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 Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/