Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <3CFB9C34.702055D5@cistron.nl>
Date: Mon, 03 Jun 2002 18:41:24 +0200
From: Ton van Overbeek <tvoverbe AT cistron DOT nl>
X-Accept-Language: en, en-US, en-GB, nl, sv
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: prc-tools-devel AT lists DOT sourceforge DOT net, johnm AT falch DOT net
Subject: text/binary problem since 20020530 snapshot
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Since the 20020530 snapshot the default mode for open is binary.
From http://www.cygwin.com/snapshots/winsup-changelog-20020529-20020530 :
> 2002-05-29  Christopher Faylor  <cgf AT redhat DOT com>
> 
>         * fhandler.cc (binmode): Default to binmode when mode is not known.
> 

This turns out to be a serious problem for a cygwin hosted cross-compiler
I am using: prc-tools (gcc for PalmOS. See http://prc-tools.sourceforge.net
for details).
A part of the C include files are supplied as part of the Palm SDK. These
are installed by a 'normal' Windows installer and have DOS cr/lf endings.
To accomodate this, the installation instructions make you install them
on a text mounted filesystem in the directory /PalmDev.
(mount -t <path to SDKs> /PalmDev)
The cross-compiler itself and the other include files are in my case
installed on a bin mounted filesystem.
The Palm supplied include files have a lot of multi-line definitions,
and now the m68k-palmos-gcc stumbles over the <cr> after the continuation '\'.
You get zillions of "stray '\' in program" messages from m68k-palmos-gcc.
This did *not* happen before the 20020530 snapshot.

Questions:
- With the behaviour since 20020503, does it make any difference at all
  if a filesystem is text or binary mounted for reading/writing when
  no mode is specified in the open() call ?
- What is the intended behaviour of a text vs binary mounted filesystem
  in the case of question 1 ?
- Depending on the answer to the 2nd question, this change might have to be
  reverted to the original 1.3.10 behaviour.

Regards,

Ton van Overbeek
P.S. While browsing the fhandler.cc code, saw a global variable binmode,
     which does not seem to do anything. What is its purpose ?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/