This is the mail archive of the
mailing list for the Cygwin project.
RE: Cross-compiling Linux kernel
- From: Fedin Pavel <p dot fedin at samsung dot com>
- To: "'Yaakov (Cygwin/X)'" <yselkowitz at users dot sourceforge dot net>, cygwin at cygwin dot com
- Date: Tue, 18 Jun 2013 10:56:09 +0400
- Subject: RE: Cross-compiling Linux kernel
- References: <003401ce6b5d$f6ec87b0$e4c59710$%fedin at samsung dot com> <51BF7465 dot 2030104 at users dot sourceforge dot net>
> > 1. Cygwin misses linux/types.h
> I have been trying to get this fixed upstream for quite some time
> without success:
Looks like Linux developers have taken over Olympus from greek gods, and
totally don't care about anyone except themselves any mote. I have already
met this problem when tried to push Amiga SFS filesystem implementation to
LKML. They told me something like: "We are *L*I*N*U*X*, we have own cool
filesystems and we don't care about one more obscure filesystem". I was
extremely angry and barely stopped myself from replying that whole their
Linux is not less obscure, because 99% of the world actually use NTFS. :(
Again, from the practical point of view... May be make some package like
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.
P.P.S. Perhaps the answer to (*) is NO, otherwise we would have fast
Samsung Electronics Research center Russia
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple