public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: news@garydjones.mailshell.com
To: cygwin@cygwin.com
Subject: Re: g++ (v.3.1.1-4)  -mno-cygwin with a hello world sample crashes oddly
Date: Wed, 24 Jul 2002 11:07:00 -0000	[thread overview]
Message-ID: <20020724110700.3fYC5uJhvTVT8PwcywFllE0GaJWBcO6mSPsKLShqUTY@z> (raw)
In-Reply-To: <20020721231949.GB4030@redhat.com>

On 22 Jul 2002, Christopher Faylor <cgf@redhat.com> wrote:

> On Sun, Jul 21, 2002 at 10:48:40AM -0700,
> news@garydjones.mailshell.com wrote: 
>>On 21 Jul 2002, Christopher Faylor <cgf@redhat.com> wrote:

>>> When I did my test case, I actually correctly
>>> did not use the -c option to try to create an executable
>>> and I never noticed the cockpit error. 

> I DIDN'T NOTICE the -c.  What part of "I never noticed the
> cockpit error" did you have problems with?

What I have "problems" with is the first part of the sentence in 
which you state that you "correctly did not use the -c option". 
That is patently absurd when you were trying to find the 
reported error - it was incorrect not to use the -c. I have left 
the quote in, should your memory fail you.

> Just to make it clear: I was no different than anyone else
> here, apparently.

Not "was", "am". Nice to see that you recognise the fact.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-07-24 15:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 13:33 news
2002-07-21 19:33 ` Christopher Faylor
2002-07-24 11:07   ` news [this message]
     [not found]   ` <E17XOVg-0007UX-00@quimby.gnus.org>
2002-07-25  4:12     ` Dylan Cuthbert
  -- strict thread matches above, loose matches on Subject: below --
2002-07-20 18:44 Dylan Cuthbert
2002-07-20 18:57 ` Christopher Faylor
2002-07-20 19:13   ` Jim George
2002-07-20 23:40   ` Dylan Cuthbert
2002-07-21  0:43     ` Robert Collins
2002-07-22  0:46     ` Gary R. Van Sickle
2002-07-21  3:39 ` Gerrit P. Haase
2002-07-21  5:54   ` Sylvain Petreolle
2002-07-21  5:55     ` Sylvain Petreolle
2002-07-21  7:59     ` Gerrit P. Haase
2002-07-21  9:51       ` Sylvain Petreolle
2002-07-21 10:00         ` Dylan Cuthbert
2002-07-21 11:49         ` Gerrit P. Haase
2002-07-21  7:39   ` Dylan Cuthbert
2002-07-21  8:01     ` Gerrit P. Haase
2002-07-21  9:58       ` Dylan Cuthbert
2002-07-21  9:58         ` Robert Collins
2002-07-21 10:48           ` Robert Collins
2002-07-21 11:53             ` Gerrit P. Haase
2002-07-21 13:12               ` Christopher Faylor
2002-07-21 13:21             ` Christopher Faylor
2002-07-21 18:37               ` Robert Collins
2002-07-21 19:49                 ` Christopher Faylor
2002-07-21 20:09                   ` Robert Collins
2002-07-22  1:39                 ` Gerrit P. Haase
2002-07-21 12:43       ` Randall R Schulz
2002-07-21 13:05         ` Gerrit P. Haase
2002-07-21 13:21         ` Christopher Faylor
2002-07-21 14:58           ` Sylvain Petreolle
2002-07-21 20:33             ` Christopher Faylor
2002-07-22  0:00               ` Dylan Cuthbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020724110700.3fYC5uJhvTVT8PwcywFllE0GaJWBcO6mSPsKLShqUTY@z \
    --to=news@garydjones.mailshell.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).