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=OuJEIDTuM7jeoGJ1OElKZxdE7V9m4kfdEJMMr6XUS6K IlhNOiCuU6YHR4bUBKQTSiSifusPbsnQAEy/GwuRpHSBhdXiKWiNsa5HJweudVTl Sjs1HFWYG5JX7vG5PkBYT8OxG35QDgxazaUUU+p0SbSZsgAnj8DadjdIHkLUDSpU = 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=rwWq85FSGRKSm6M5WdAaOPcEEe4=; b=ov5caGFuTllLpBMMn h6DeD3ZLZPIAMzOhPXkS/ymPc2iCQZXkJVp4/3GiqbL2JpN+mWLVV5Y0GI72HvrE pkRuyoH38S4Fdrzs6OkmrJVO0u65czmjhHtLHs164EMK8dQU2jIlGIOA+c3YDgsa 8EbP8l7xSSWruwcuaYTX138zMU= 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=-3.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 Message-ID: <517ADF9C.4000606@cwilson.fastmail.fm> Date: Fri, 26 Apr 2013 16:12:12 -0400 From: Charles Wilson 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: Attn: JonY -- 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> <51630442 DOT 4080805 AT cwilson DOT fastmail DOT fm> <20130409091609 DOT GI10126 AT calimero DOT vinschen DOT de> <51641548 DOT 2060700 AT cwilson DOT fastmail DOT fm> <20130409135842 DOT GC15271 AT calimero DOT vinschen DOT de> In-Reply-To: <20130409135842.GC15271@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hey, JonY --- On 4/9/2013 9:58 AM, Corinna Vinschen wrote: > On Apr 9 09:19, Charles Wilson wrote: >> On 4/9/2013 5:16 AM, Corinna Vinschen wrote: >>> On Apr 8 13:54, Charles Wilson wrote: >>>> 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. >>> >>> The absence of intrin.h was a bug, but otherwise you could still use >>> the ddk headers for what they are supposed to be: Writing device >>> drives and other kernel stuff. The difference is just that the ddk >>> headers from mingw-w64 cannot be used together with the user space >>> headers like windows.h, but that's not different from "upstream". >> >> ...but is it reasonable to create a *cygwin* device driver or kernel >> mode item? If you're using the cygwin compiler, then you're linking >> against the cygwin dll -- which makes a bunch of usermode w32 calls >> under the hood. If it's bad juju to mix ddk/ kernel mode stuff with >> w32api/ user mode stuff, then any "cygwin" device driver is, by >> definition, bad juju. >> >> If I'm correct, then the *cygwin* w32api-headers package (and >> cygwin64-w32api-headers) should exclude ddk/ from their deliverable >> footprint, even if intrin.h is added back to the toplevel w32api/ >> include directory for other reasons. > > Well, actually I don't really care one way or the other. You may want > to discuss this with JonY. Any thoughts on this -- the idea that the cygwin (and cygwin64) package of w32api-headers w32api-runtime should be stripped of any ddk-related items, as they can't actually be mixed with the usable-from-cygwin user mode w32 items? Arguably this might break some things -- such as the (old version of) csih/getVolInfo -- but they are actually already broken, with the (bug or compile failure) just waiting to be exposed. -- 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