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=io1YmHVdxKVKydk0+GqC/o/PbY5V8hgHcL60SjSD9LYF3EydWlb7o
	6RExNbr9Fc5H1Dwa3ComGHK5tvoc5I8+8gSns9MjwjzFLEokDfJ6SssuEphYMQlr
	yYKvyE46mpAF9HORiz9BRgF/f5T9NTf+fBg7L8t+iHuSSZ5ZvAf3RE=
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=3+bSHhIMrpS2Zvn0y4uYx71NwD4=; b=jPTI1o/82hYEYlhyvnyXUOvFnsbi
	4BtksIL/Pjv0xM1T+Crqn0rG8ujggRoNGXzr79IjFSBZWV6OKhf7Oi8OS9/LWjNU
	i8boFgdljh7GCA7GGS6zMQOvosLGix5Hum0QbzSyySKB8XbFMIy/qSTKNMM7OGhj
	YvrEO7oAkzwEcPA=
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=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX181AmRSLJcNuu+fE+1Aq3FR
Date:	Tue, 18 Jun 2013 10:33:08 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cross-compiling Linux kernel
Message-ID:	<20130618143308.GB5406@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<003401ce6b5d$f6ec87b0$e4c59710$%fedin AT samsung DOT com> <51BF7465 DOT 2030104 AT users DOT sourceforge DOT net> <001301ce6bf0$ea4904a0$bedb0de0$%fedin AT samsung DOT com> <20130618101706 DOT GB27405 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20130618101706.GB27405@calimero.vinschen.de>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Tue, Jun 18, 2013 at 12:17:06PM +0200, Corinna Vinschen wrote:
>On Jun 18 10:56, Fedin Pavel wrote:
>> [...]
>>  P.S. I have got even more crazy idea, perhaps deserving a separate topic...
>> BSD systems have Linux binary compatibility layer. Could we have one ?
>> Technically this depends on ability to construct process image manually in
>> Windows (*). Is it possible (using NT API of course) ? And, of course,
>> someone needs lots of spare time to code this. :) OTOH, CoLinux already does
>> this (yep, they are not 64-bit for now...), so perhaps there's no need to
>> duplicate the job done.
>
>Not in the Cygwin DLL.  As an extra DLL layer I don't have a problem
>with that.

There was a project out there many years ago which did this.  You could
run simple linux binaries on Windows.  I offered to host the development
on sourceware.org (aka cygwin.com) but, IIRC, the developer never
responded.

I don't remember what the name of the project was and I'm sure that it
won't work with more modern versions of Windows but it is a cool idea.

cgf

--
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

- Raw text -