Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A641E38.3F2A03B6@cern.ch> Date: Tue, 16 Jan 2001 11:11:04 +0100 From: "Lassi A. Tuura" Organization: Northeastern University, Boston, USA X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Joey Mukherjee CC: cygwin AT sources DOT redhat DOT com Subject: Re: Problem with F:/ and /cygdrive/f/ solved! References: <000501c07f27$8a783640$2397a281 AT marisa DOT space DOT swri DOT edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > However, is O_BINARY a standard flag for open? Adding that flag on Solaris > seems to fail in compile since that symbol is not defined or mentioned in > the open man page. I'd hate to add #ifdef around every open... Once per file is enough (or put it into your config.h for the whole project): #ifndef O_BINARY # define O_BINARY 0 #endif Or-ing it with other flags for `open' is then harmless on platforms that don't know anything about the distinction of binary and text files. Cheers, //lat -- People demand freedom of speech to make up for the freedom of thought which they avoid. --Kierkegaard -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple