X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,TW_YG X-Spam-Check-By: sourceware.org Message-ID: <4C375753.1070709@cwilson.fastmail.fm> Date: Fri, 09 Jul 2010 13:07:31 -0400 From: Charles Wilson Reply-To: cygwin-apps AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com, cygwin-apps AT cygwin DOT com Subject: Re: cygport cross compile(r) support [was: Re: cygport patch: suppress libtool fixup step] References: <1278402537 DOT 5784 DOT 8 DOT camel AT YAAKOV04> <4C337C6E DOT 2080003 AT cwilson DOT fastmail DOT fm> <1278455320 DOT 4032 DOT 49 DOT camel AT YAAKOV04> <4C33EEC1 DOT 9050600 AT cwilson DOT fastmail DOT fm> <1278519024 DOT 1096 DOT 90 DOT camel AT YAAKOV04> <4C34D3BF DOT 7020404 AT cwilson DOT fastmail DOT fm> <1278548055 DOT 6960 DOT 59 DOT camel AT YAAKOV04> <4C3534E6 DOT 90505 AT cwilson DOT fastmail DOT fm> <1278560355 DOT 6960 DOT 114 DOT camel AT YAAKOV04> <4C35E1E1 DOT 1080906 AT cwilson DOT fastmail DOT fm> <20100709165459 DOT GB25913 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20100709165459.GB25913@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 7/9/2010 12:54 PM, Christopher Faylor wrote: > On Thu, Jul 08, 2010 at 10:34:09AM -0400, Charles Wilson wrote: >> On 7/7/2010 11:39 PM, Yaakov (Cygwin/X) wrote: >>> On Wed, 2010-07-07 at 22:16 -0400, Charles Wilson wrote: >>>> Hmm. That's what I *was* doing: JonY's -src provides a cygport that >> >>> I didn't mean the .cygport(5), I meant cygport(1). The goal is to make >>> these workarounds unnecessary. >> >> Sure. There's three "status levels" of cygport support for any desired >> behavior: > > I'm getting whiplash trying to read about these issues in cygwin-apps and > cygwin. If Yaakov doesn't mind, I'd like to make discussions of cygport > on-topic in cygwin-apps. It's sort of been that way for a while now anyway. Ack. And thank you! This whole complex of issues is a single discussion; it makes little sense to spread them around. I'll confine future response to any of these related threads to apps. -- Chuck -- 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