Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Tue, 28 Dec 1999 10:47:39 -0500 From: Christopher Faylor To: stefan Cc: Christopher Faylor Subject: Re: filedescriptors and sockets Message-ID: <19991228104739.A10377@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: stefan , Christopher Faylor References: <19991227152919.A25954@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from stefan@linux.f1.fhtw-berlin.de on Tue, Dec 28, 1999 at 12:51:24PM +0100 On Tue, Dec 28, 1999 at 12:51:24PM +0100, stefan wrote: >On Mon, 27 Dec 1999, Christopher Faylor wrote: >>Cygwin does not make a distinction between sockets and normal file >>descriptors. It's should work just like UNIX. > >I compiled the program with the -mno-cygwin option. And there the >select() statement return an error if there are "normal" >filedescriptors (from a _pipe()) in the field. Why is this ? In the above sentence "Cygwin" is meant to imply that you are actually *using* Cygwin. You are not, of course, using Cygwin if you specify the -mno-cygwin option. Normal Windows (i.e., what you're accessing when you specify -mno-cygwin) does not provide a select() that can use pipe "file descriptors", AFAIK. -Christopher Faylor -Cygwin Engineering Manager -Cygnus Solutions -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com