From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22925 invoked by alias); 19 Jun 2013 18:38:12 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 22915 invoked by uid 89); 19 Jun 2013 18:38:11 -0000 X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-pb0-f48.google.com (HELO mail-pb0-f48.google.com) (209.85.160.48) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 19 Jun 2013 18:38:06 +0000 Received: by mail-pb0-f48.google.com with SMTP id ma3so5347425pbc.35 for ; Wed, 19 Jun 2013 11:38:05 -0700 (PDT) X-Received: by 10.69.15.67 with SMTP id fm3mr4059040pbd.54.1371667085236; Wed, 19 Jun 2013 11:38:05 -0700 (PDT) Received: from [192.168.0.101] (S0106000cf16f58b1.wp.shawcable.net. [24.79.212.134]) by mx.google.com with ESMTPSA id ka16sm19494985pad.14.2013.06.19.11.38.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 11:38:04 -0700 (PDT) Message-ID: <51C1FA8E.3000307@users.sourceforge.net> Date: Wed, 19 Jun 2013 19:27:00 -0000 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Adding MSYS functionality to Cygwin References: <51C0B08E.8080900@etr-usa.com> <51C0D956.4090905@etr-usa.com> <51C1B299.1000701@cwilson.fastmail.fm> <51C1F0F9.70601@etr-usa.com> In-Reply-To: <51C1F0F9.70601@etr-usa.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-06/txt/msg00518.txt.bz2 On 2013-06-19 12:57, Warren Young wrote: >> Not all packages are cross-compiler-compatible. > > Is that another way of saying that not all packages use autotools? :) autotools can certainly make cross-compiling easier than most other build systems, but it's not a guarantee either. For instance, anything that requires in-tree compiled executables to run (e.g. AC_RUN_IFELSE configure tests, GObject Introspection generation, etc.) requires either workarounds, or simply cannot be cross-compiled. > You're not talking about anything different than the sort of thing > Cygwin package maintainers go through, sometimes needing to arm-twist > odd build systems to behave according to cygport's expectations? I think you mean Cygwin's expectations? Yaakov -- 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