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: Sun, 21 Jul 2002 13:33:00 -0000	[thread overview]
Message-ID: <1027273720.3d3af3f88166e@www.mailshell.com> (raw)

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

> On Sun, Jul 21, 2002 at 08:00:48AM -0700, Randall R Schulz
> wrote:

>>When you use the "-c" option, you suppress the whole linking
>>phase. The output, regardless of its extension, is not a
>>binary executable
[snip]
> Wow, all of this traffic and Randall is the first, AFAICT,
> to notice that someone was using the -c option incorrectly. 
> 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.

The reason being that you were trying to reproduce a reported problem and failed to faithfully reproduce the conditions described.

> There are something on the order of 22 messages in this
> thread and it looks like only one person actually noticed
> the obvious problem. 

So obvious that you didn't comment on it in your original response? Since yours was the first reply, you could have saved 20 of those messages by doing so.

_______________________________________________________
The FREE service that prevents junk email http://www.mailshell.com

--
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-21 17:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 13:33 news [this message]
2002-07-21 19:33 ` Christopher Faylor
2002-07-24 11:07   ` news
     [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=1027273720.3d3af3f88166e@www.mailshell.com \
    --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).