This is the mail archive of the
mailing list for the Cygwin project.
Re: Cross-compiling Linux kernel
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 18 Jun 2013 12:17:06 +0200
- Subject: Re: Cross-compiling Linux kernel
- 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>
- Reply-to: cygwin at cygwin dot com
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
> P.P.S. Perhaps the answer to (*) is NO, otherwise we would have fast
That's not quite correct. The problem is not utilizing the native NT
functions to create a process image, the problem is that the Win32
libraries like advapi32, msvcrt, etc, which are directly or indirectly
loaded into a Cygwin process, are not capable to deal with a process
clone situation. They were never designed this way and there's not much
chance they will ever get a revamp, just to allow Cygwin to create a
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple