X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Tue, 9 Sep 2008 17:59:14 -0400 From: "Mark J. Reed" To: cygwin@cygwin.com Subject: Re: Help on dos2unix In-Reply-To: <72B97F56A23E3844BB0DEC054CD85C39067A1D64@ltssvex10.lts.liebherr.i> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <72B97F56A23E3844BB0DEC054CD85C39067A1D64@ltssvex10.lts.liebherr.i> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, Sep 9, 2008 at 10:48 AM, Heude Pascal (LTS) wrote: > I am using the command dos2unix to convert file from DOS to UNIX in a makefile. If that's the Cygwin version of dos2unix.exe, then I assume you are also using the Cygwin version of make, which you are in turn running from a Cygwin bash shell? > But I get the return code 128 from the command Exit code 128 is a "something went wrong but I'm not sure what" signal. Usually, exit codes above 128 mean that the process was killed by a fatal signal, whose number you get if you subtract 128. But there's no fatal signal 0, so 128 is sort of a default "execution environment not working right for that command". Hence my suspicion that some non-Cygwin component is at work here. -- 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/