DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=l3b
	kdEE4V1hGOcdk6qLje+Z4AzPgfLxBTfQ8Es//SVa1oelyccr3oVTOIy5LT0yPt84
	smsR+vIFHn4nsQgZWT44Fedaj2YMP3m6Iqw6G6DKrUW69+5r25IuQtB7XTjHutM6
	AfJmQCQn9XLtzyFsR6MG3Fv/CbDXq2YXIajfGm8U=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Fedin Pavel <p.fedin@samsung.com>
To: cygwin@cygwin.com
Subject: Cross-compiling Linux kernel
Date: Mon, 17 Jun 2013 17:24:15 +0400
Message-id: <003401ce6b5d$f6ec87b0$e4c59710$%fedin@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit

 Hello!

 In order to cross-compile Linux kernel i have to patch host-side tools a
little bit. Current problems are:
 1. Cygwin misses linux/types.h
 2. Cygwin defines the following ELF macros according to host machine:
ELF_ST_BIND, ELF_ST_TYPE, ELF_R_SYM, ELF_R_TYPE

 What about improving Linux compatibility ? We could have own version of
linux/types.h (for __u8. __u16, etc), and omit ELF definitions. AFAIK they
are not used anywhere, they are just inherited from BSD.
 At the other hand, i believe the same problem will happen if i try to
cross-compile Linux kernel under BSD. And Cygwin is BSD-style system...

 Just decided to drop this in as one more "what if...".

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia


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