Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Thu, 15 Jan 2004 13:23:16 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Problem compiling cygwin1.dll from CVS Message-ID: <20040115182316.GB16598@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <1074109551.959.19.camel@taz.graycell.biz> <20040115165423.GC14681@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Note-from-DJ: This may be spam On Thu, Jan 15, 2004 at 12:15:15PM -0500, Igor Pechtchanski wrote: >On Thu, 15 Jan 2004, Christopher Faylor wrote: >> Nope. I routinely build cygwin with text mode mounts with no problems >> at all. I don't know why you were having problems but we're certainly >> not going to document a bug. > >This is not a text mode mount problem. This is a problem of downloading >files in text mode, and then transferring them over to a binary mount >(without appropriate conversion), so you get CRLF files on binary mounts. >Which is a peculiar (and, IIUC, unsupported) mode of operation. FWIW, I >agree with CGF - this doesn't merit documenting. It's in the archives, >anyway. What probably needs documenting is what the letters in "FAQ" stand for. No, wait. That's probably there already. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam@sourceware.org and be permanently blocked from mailing lists at sources.redhat.com -- 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/