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]

It does involve cygwin

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:
Unsubscribe info:

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