From: Mumit Khan <khan@xraylith.wisc.edu>
To: Charles Wilson <cwilson@ee.gatech.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: <Pine.SUN.3.93.981015161515.12680B-100000@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <3626408A.E9CB5065@ece.gatech.edu>
On Thu, 15 Oct 1998, Charles Wilson wrote:
> 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.
If you haven't seen my followup to Earnie's 2nd posting on this, it'll
soon show up on the list and I won't repeat myself.
I'll summarize quickly: GCC has *always*, and still does, called the C++
compiler when it sees certain suffix, and still does. That has nothing to
do with linking however, and GCC has *never* linked in the C++ runtime if
invoked as gcc as opposed to g++/c++.
The only difference in gcc-2.8.0 is that g++ no longer links in the
deprecated libg++ automatically. Before 2.8.0, c++ will only link in
libstc++ and g++ will add libg++ in addition to libstdc++. Now, both
c++ and g++ are identical in behaviour.
It is not a bug, and the behaviour remains the same (minus, and possibly
plus, a few bug fixes in how the driver works). Of course, I'm talking
about gcc2 days; g++ 1.x was a different beast altogether.
I do sympathize with folks who misunderstand how the language drivers in
gcc is supposed to work; the documentation is not at all clear, and I
obviously haven't done anything to improve it.
Any followups to gcc or egcs related mailing lists please.
Regards,
Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent 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
1998-10-15 21:47 ` Mumit Khan [this message]
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=Pine.SUN.3.93.981015161515.12680B-100000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cwilson@ee.gatech.edu \
--cc=earnie_boyd@yahoo.com \
--cc=gnu-win32@cygnus.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).