X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=GRX92qFy8DXe0jJb0Eg3kfPqmum4q
	SH9TwV5/zuFGf/3XYRpt6I+gp5/UJ6NABIWhftXY6x83EYJB/hOrMBIgdePfSv7x
	+70iYqs/aYvBEMq5Q7kfOTdYiNe1O5kPjs52vFU6NFQDPWRDrXGjfyJ0iEg8R+PP
	0hZaF4BgfldR+8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; s=default; bh=QshQ2FULJWftZv+S7SR1dIxCHn8=; b=wjf
	TrKFkO1thh2bJbUCkwzseg5hkzlFrZbVqhwDQHlT1khG3BtG56tnqHQrfUtHfh7p
	TwT0pPJQDf4BvCwwBqSgVhsms+19sv/ehMsPkW9rFFWWleEDHLmSu24S8S+bGFWa
	RJ8AAcfdGHfd8pM1dvgJjhUN6Gb5ayrbLWCe7/i0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RDNS_NONE,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-pa0-f42.google.com
X-Received: by 10.68.196.69 with SMTP id ik5mr18395745pbc.132.1383967301594; Fri, 08 Nov 2013 19:21:41 -0800 (PST)
MIME-Version: 1.0
From: Jason Gross <jasongross9@gmail.com>
Date: Fri, 8 Nov 2013 22:21:11 -0500
Message-ID: <CAKObCaoCpoUf+3SFO96FcHS73yYoKKTN=yP5RdMScdg5x8ka+g@mail.gmail.com>
Subject: Help with getting binaries to not print ^M
To: cygwin <cygwin@cygwin.com>
Content-Type: text/plain; charset=ISO-8859-1

I have some precompiled binaries (from, e.g., ocaml, gtk+).  When I
install them to a location like D:\OCaml\bin and run them, the output
has a ^M at the end of every line.  When I copy the binaries to a
cygwin path (something that doesn't get translated to /cygdrive/),
they work fine.  This messes with all of my build scripts, which
except things like `ocamlc -where` not to have a trailing ^M.  So I
tried moving them to D:\cygwin64\, and this fixed some of the
problems, but it's still broken in some cases, like when `ocamlc
-where` gives "D:/cygwin64/OCaml/lib" and then a build script later
calls `D:/cygwin64/OCaml/bin/ocamlc -where`, and the ^M's come back.
It seems very broken to me that the output of an executable should
depend in this way on how it's called.  If it's relevant, I updated
cygwin-x86_64 earlier today, and mount gives me
$ mount
D:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
D:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
D:/cygwin64 on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto)
E: on /cygdrive/e type ntfs (binary,posix=0,user,noumount,auto)
Y: on /cygdrive/y type afs (binary,posix=0,user,noumount,auto)
Z: on /cygdrive/z type afs (binary,posix=0,user,noumount,auto)

Anyway, I'd like to know how to fix this without manually sticking in
code to strip ^M in all of my build scripts.

Thanks in advance.

-Jason

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

