X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	cygwin AT cygwin DOT com
Subject:	Re: Fixing the state of C++ in Cygwin
Date:	Mon, 17 Apr 2006 03:52:05 +0000
Message-Id:	<041720060352.4350.444310E500004BAC000010FE22058861720A050E040D0C079D0A@comcast.net>
X-Mailer:	AT&T Message Center Version 1 (Apr 11 2006)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> > The cause of this is apparently /tmp being a textmode mount.  If
> > switched to binary, cat << EOF works as expected.  Is that really what's
> > supposed to happen?  It doesn't seem right that a system configured to
> > act binmode is going textmode just due to using '<< EOF' syntax.
> 
> That sounds like a bash bug to me.  The type of mount of /tmp should not
> affect "heredoc"s.

For here-docs inside complex commands, bash uses /tmp to create a
temporary file holding the here-doc contents.  I will look into forcing
bash to use binary mode on temp files - expect a new release soon
(and I was just about ready to upload bash-3.1-5 when my hard drive
crashed yesterday; so when I respin it, I will make sure I catch this
issue.  Fortunately, I did not lose very mush else).  Thanks for the
diagnosis of the problem!

-- 
Eric Blake
volunteer cygwin bash maintainer

--
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/

- Raw text -