X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 21 Aug 2008 23:10:39 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Building kernel modules Message-ID: <20080822031039.GA15900@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <48AD7E49.9080908@cygwin.com> <48AD85FF.2050504@cygwin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, Aug 21, 2008 at 11:20:29PM +0200, Bosko Radivojevic wrote: >From my perspective it looks like a cygwin "problem". Sorry if I'm not righ. > >Probably sys/types.h in cygwin and Linux are not the same, something >that is defined in linux/types.h in linux is also defined in >cygwin/types.h, etc. I can probably copy /usr/include from my Linux on >the Cygwin host, and probably I will be able to cross-compile kernel, >except the things that should be compiled for the host (cygwin in my >case). > >Any comments? You have a lot of "probably"s above which seem like they would be fairly easy to corroborate. Why don't you actually check the details that you mention rather than relying on people where who have already admitted to knowing little about this subject? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/