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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=DN0q6lqYbYEuJG8Xfc+DINnyWM7qcQ6JSkQGvW1xW+2Y0FJPV4CIN Wnh+44k7F1UBbySoJ00nfHvW9THgpNhP3yh2b9RYaXmLkHr6EOVe/j+Xe0t8PBme 469v16HzTKHeRxXEQsmf4H5rpdho2urbO/AjIp81tWmRBRz1FNLoYQ= 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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=kwaDDQz0eItEwqZv/r+NAuijjmc=; b=euYhueq/3AA/AxKFX55U5Uvrp8mv unLiOr9JtouKuds3bj5T0Lt9Oyh25qa6lMQu71Rvtz9BIYaPcEXxqF+trNxOcq7N mEdVOhxqe10Q3VMViakufApOEUVZ9R7SM/6YdzNji/OjM5TY48P0lXCvkzqwQ91l mwEsTOhzRW8GMN0= 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=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Date: Tue, 9 Apr 2013 15:58:42 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Bug in ddk headers when used from cygwin Message-ID: <20130409135842.GC15271@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51641548.2060700@cwilson.fastmail.fm> User-Agent: Mutt/1.5.21 (2010-09-15) 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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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