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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=luqY3hPWj7lnzigl/trE2BYLkYWqKlgEDRA4Soms9Ol 4oI+r4lsejt0JxHtY2tDNGx5FFBuFSssobTNX/H/LG6K7BowLR/IrZZwVazS6kIF RhOZcdgjwcx2EHjh1TIe809a1JpPAddUy4DJV5LYsYaQMXwyeqmk1Cu63eFU39us = 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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=B0pSFc5ayxVq8+EC/h0hmlGHxl0=; b=lNVt9mqve3q9gU5cg qblD9bg5nqJFu5PEGKYLIimTcMcLL/Wwb0WHo/leJ3xZsWLHRPvxKlLofvC4vlxR rakJKWBx45RXfFhEe6wjBQ4JsDlgNVE2j+ltUaB+t/LN8eZ4elmCMWNW6UPS/iTC addOCLAQKKsEhK8srg/9Fm+oqc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: <cygwin.cygwin.com> 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 X-Spam-SWARE-Status: No, score=-5.8 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO autolearn=ham version=3.3.1 Message-ID: <51630442.4080805@cwilson.fastmail.fm> Date: Mon, 08 Apr 2013 13:54:10 -0400 From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Bug in ddk headers when used from cygwin References: <51625CAE DOT 2030703 AT cwilson DOT fastmail DOT fm> <20130408074801 DOT GA10199 AT calimero DOT vinschen DOT de> In-Reply-To: <20130408074801.GA10199@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 4/8/2013 3:48 AM, Corinna Vinschen wrote: > On Apr 8 01:59, Charles Wilson wrote: >> Any suggestions for a fix? > > Yes. Do not use the ddk headers with Cygwin. Not only that intrin.h is > really missing(*), the ddk headers in mingw-w64 are not fit for usage in > user space code. For that reason the latest Cygwin code does not use > these headers either. > > There are two user space headers exposing ntdll stuff, winternl.h and > ntdef.h. They partially contradict each other so they can't be used in > parallel. Usage of winternl.h is preferred. Wintern.h isn't exactly > set in stone upstream, so additions and fixes are welcome. > And, as a side note, <ddk/ntstatus.h> from mingw32 became just > <ntstatus.h> in mingw-w64. OK, I'll try to figure out what getVolInfo was using from ddk, and see if I can replicate the functionality with pure w32api non-ddk stuff. I'll also have to ask the original developer what she was thinking, relying on ddk internals... :-) But doesn't this mean that the cygwin's w32api package should exclude all of the ddk headers; it's not simply a case that you "shouldn't" use ddk/*.h, but that you actually cannot, because compilation will fail. -- Chuck -- 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