X-Spam-Check-By: sourceware.org X-SBRS: None X-IronPort-AV: i="4.09,245,1157353200"; d="scan'208"; a="149907556:sNHT21766178" Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Similar Bash 3.1.18 CR/LF Problem Date: Mon, 2 Oct 2006 13:14:37 -0700 Message-ID: <657A9BE009D3504AAE29BD8E8C2DD61E01A5ABFD@SDGEXEVS02.corp.intuit.net> In-Reply-To: <20061001013338.GE1459@trixie.casa.cgf.cx> From: "Wilks, Dan" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k92KEkr5011211 > > I really am getting a bad feeling that, rather than FIXING THE SCRIPTS, > everyone is reverting to using text mode mounts which are not what we > generally recommend. > > cgf > As much as I would love to work in a pure cygwin environment it's not always possible. In our particular case the scripts are generated by the Win32 port of gnu's make. It really wants to put a cr/lf on the end of the shell script it makes and invoke sh passing it the DOS pathname of that script. I'd love to be able to use cygwin's make, but it's just not practical. -- 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/