X-Recipient: archive-cygwin AT delorie DOT 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:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=bZ tLoJabVnMEwqc+m4T4uNrQwJmbgQCs1+NPnsquWFyK2jgTnJtEeqRKQXM27OId8n 6/dGA7m5qWsz8QDLCkb/x7+HYbLT+xkOO8Uu6EIsBZv1lBEaULtGnmuk5bd7NieN 1KZUCsIWVqfgBv8FsyG/wk0OqbPZuk63usxXF5DPE= 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:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=JwS7EFfd PgWn19JauW4+LhGgzsQ=; b=HdZrtRfCzXInWFl0c6rntSLdbVse2P5SyspylKPU mrqXXPxw/uUOFQQJwndJq1p+emzaAH2B3ftDgvciUPwAMpdhrQmB4icCPgk5/dHC xEMQbzPnUjJdoKw6zlLo4LpxsfSIXAD3/WJUmK1sJhrF8EWHy43Gisr2uo2HJ05i xDI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.50.45.97 with SMTP id l1mr15918530igm.99.1367566469031; Fri, 03 May 2013 00:34:29 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 May 2013 09:34:28 +0200 Message-ID: Subject: Re: Cygwin64: errno.h error values From: Kai Tietz To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 2013/5/3 Jan Nijtmans wrote: > 2013/5/3 Christopher Faylor: >> We make ABSOLUTELY no guarantees that our errnos will match any other >> system's. You can't expect that you will be able to use Cygwin errno's >> in pure Windows applications. We really don't care if our errnos match >> those of Windows. Sorry. > > No need for a sorry. I understand. I just felt obliged to report it, because in > the (unlikely) case that such a problem arises a major release is the > only moment that such a thing can be fixed. This would be a chance > to have a single errno.h shared by mingw, mingw-w64, wine and cygwin > (which would then be a superset of Microsoft's). > > The mingw-w64 cross-compiler in Cygwin64 (x64_64-w64-mingw32) > is currently lacking "errno.h", Absoultely an absurdity. Of course mingw-w64 provides an errno.h header. Not sure where you expect headers are and what content by your expectations they shall have, but I would recomment that you might try before starting to do fural guessings. Regards, Kai PS: The native toolchain and cygwin don't share most of the C-runtime-headers by good reasons. -- 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