X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:cc:subject; q=dns; s=
	default; b=oGrysxB/E2R2OHZ3X4LZNNvE+mEIac6G5SDAKXEjq5UElGrxAeFAU
	YlzQJ3TXz7BEhcRKyOeUnDeKomAazoJeAYAsWx2BWhk3JJBV0Kcg58PaTX4SKb3e
	3+pcniMbPzjlSQA16ukYVi6ccw1N127dtKRmKi2DajEEx5DvirCqkI=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:cc:subject; s=default;
	 bh=3ZBgDfpIowTI9pRM/sHFWlBqPro=; b=xpWeX1xBTr8YIkaXJbd1eBxcLGFn
	EEFYGLywXcekSKY0MmtYGwLqvb6BKVJmd+/g94bz40n5e9zXssG27w78adBu069X
	pM6sEU3KT93j1m5d0eXtGRbRDD+vpH/6V90VKBHxPVR/fuliyfn+8jns83k6i6DN
	bdj7lCKlYmGM21g=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HDRS_LCASE,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,SPF_NEUTRAL autolearn=ham version=3.3.1
Message-ID: <20130405143845.2468@binki>
Date: Fri, 05 Apr 2013 14:38:45 +0900
From: wynfield@gmail.com
To: <cygwin@cygwin.com>
cc:
Subject: It does involve cygwin (last message hopefully)


Comments inlined.

Christopher Faylor wrote:
> On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote:
> >On 4/4/2013 2:40 PM, Eliot Moss wrote:
> ....snipped
> If you have to enter MinGW land to perform what the OP wants then that
> is a really clear indication that this is off-topic.

That is illogical, just because the very good advice above explains a method of how it could be done using another system, does not make it irrelavant to cygwin.   That's like saying compiling can be done with Microsoft C, so  gcc is not relevant to cygwin.

> I think we've seen an adequate amount of advice for how the OP can
> proceed.  There was a suggestion that one could look at the disassembled
> output from gcc to see how it does things.  That's probably the best
> advice for how to proceed, regardless of the platform.
Does this mean that you'll honor your word and take it off line to answer practical questions regarding this issue?


- end

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

