This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: It does involve cygwin


On Fri, Apr 05, 2013 at 02:37:11PM +0900, wynfield@gmail.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:
>> ....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.

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.

cgf

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]