public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ee.gatech.edu>
To: Mumit Khan <khan@xraylith.wisc.edu>
Cc: Earnie Boyd <earnie_boyd@yahoo.com>, gw32 <gnu-win32@cygnus.com>
Subject: Re: BUG: egcs-1.1-mingw32 - gcc -o hello hello.C
Date: Thu, 15 Oct 1998 21:47:00 -0000	[thread overview]
Message-ID: <3626408A.E9CB5065@ece.gatech.edu> (raw)
In-Reply-To: <Pine.SUN.3.93.981014110606.10933F-100000@modi.xraylith.wisc.edu>

Mumit Khan wrote:

> On Wed, 14 Oct 1998, Earnie Boyd wrote:
>
> > When giving this command with mingw32 version of egcs-1.1 the stdc++
> > library isn't properly included at the execution of ld.  This is the
> > only problem with this command.
> >
> > g++ -o hello hello.C will properly add the library.
> >
>
> Hi Earnie,
>
> I'm a bit confused ... "gcc" is the C driver, and "g++" or "c++" is the
> C++ driver. "gcc" will not and should not C++ specific libraries, and the
> only correct and portable way to link C++ programs is to use the "c++" or
> "g++" driver. If "gcc" adds C++ specific libraries, it's a bug, not a
> feature.
>
> Correct way to link C++ programs:
>
>   $ c++ -o hello hello.cc
>
> (or alternatively use g++, which is just a link to c++).
>

<snip>

Up until recently, I believe that gcc when called on a c++ source file,
would call g++, and everything would be fine. This broke at gcc 2.8.0 on
HP-UX, so now you have to call g++ explicitly. I don't know the heritage of
egcs, but it could have inherited this behavior, and thus (egcs) gcc does
not helpfully call (egcs) g++ for you.

--Chuck


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1998-10-15 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-14 10:16 Earnie Boyd
1998-10-14 10:41 ` Mumit Khan
1998-10-15 21:47   ` Charles Wilson [this message]
1998-10-15 21:47     ` Mumit Khan
1998-10-15  6:06 Earnie Boyd
1998-10-15  6:06 ` Mumit Khan

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=3626408A.E9CB5065@ece.gatech.edu \
    --to=cwilson@ee.gatech.edu \
    --cc=earnie_boyd@yahoo.com \
    --cc=gnu-win32@cygnus.com \
    --cc=khan@xraylith.wisc.edu \
    /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).