This is the mail archive of the
mailing list for the Cygwin project.
Re: It does involve cygwin
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 5 Apr 2013 01:45:16 -0400
- Subject: Re: It does involve cygwin
- References: <20130405143711 dot 3384 at binki>
- Reply-to: cygwin at cygwin dot com
On Fri, Apr 05, 2013 at 02:37:11PM +0900, email@example.com wrote:
>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:
>> 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.
Perhaps you should read the description of what is on-topic for this
list at http://cygwin.com/lists.html .
>> 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?
Now you're sounding delusional.
Please stop this. First and only warning.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple