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=dcv
	jfYmVPxUSh1wpisTMQf69P+x2/zwEU/TwWEQdBVjoDGRjTiNuvANImxxE4FUCP/l
	m/afIbdmYieQVvpY0A+enz8uNvRY+IpQxI0YvH63Bg35AK6xcuzgq0KtqsFq8zaH
	tfCPRJOD7N4+QSdGn9ibSW8xMsf1B972nbbuDq64=
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: Suggestion: improve cross-compiling ability
Date: Mon, 08 Jul 2013 16:07:12 +0400
Message-id: <000901ce7bd3$ae02fb70$0a08f250$%fedin@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit

 Hello! I have got one small idea on how to improve compatibility with
cross-compiling Linux software. This time it's glibc.

 At certain point glibc's rpcgen program (which is being compiled for host),
relies on '#ifndef __u_char_defined' and '#ifndef __daddr_t_defined' in
order to determine presence of 'u_char' and 'daddr_t' respectively (see
libc/sunrpc/rpc/types.h). I have to patch this to add _BSDTYPES_DEFINED
check in order to be able to cross-build glibc under Cygwin.
 What if we add also these Linux-style definitions to our includes ?

 P.S. I understand that actually it's glibc needs fixing because the same
will happen on any other non-Linux OS. But i believe FSF will simply say "we
don't care" and won't accept this fix.

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