All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schiele <rschiele@uni-mannheim.de>
To: deedsmis@aculink.net, linux-gcc@vger.kernel.org
Subject: Re: Mistake With CPP File
Date: Thu, 1 Aug 2002 15:33:42 +0200	[thread overview]
Message-ID: <20020801133342.GA32311@schiele.local> (raw)
In-Reply-To: <3D48F387.24495315@cdm01.deedsmiscentral.net>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

On Thu, Aug 01, 2002 at 02:38:32AM -0600, SoloCDM wrote:
> Robert Schiele stated the following:
> > cout is in libstdc++. So either you have to call "g++ fig01_02.cpp" or
> > "gcc -lstdc++ fig01_02.cpp".
> 
> It worked -- Thanks!
> 
> I couldn't help but notice how g++ linked all the way back to
> colorgcc.  Although, colorgcc doesn't react like g++.  Colorgcc won't
> create a.out.

Sorry, but I cannot see what you wanted to tell us with this
paragraph.

> What is gcc used for?  I noticed it seems to have some of the same
> files or libraries as g++.

gcc and g++ are the same, but gcc uses C as it's standard language,
where g++ uses C++ as standard language and links standard C++
libraries without the need to specify them explicitly.

Robert

-- 
Robert Schiele			Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker	mailto:rschiele@uni-mannheim.de

[-- Attachment #2: Type: application/pgp-signature, Size: 524 bytes --]

  reply	other threads:[~2002-08-01 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 11:04 Mistake With CPP File SoloCDM
2002-08-01  7:09 ` Robert Schiele
2002-08-01  8:38   ` SoloCDM
2002-08-01 13:33     ` Robert Schiele [this message]
2002-08-02 12:47       ` SoloCDM
2002-08-02 13:08         ` Robert Schiele
2002-08-02 18:18           ` SoloCDM
2002-08-02 21:40             ` Robert Schiele

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=20020801133342.GA32311@schiele.local \
    --to=rschiele@uni-mannheim.de \
    --cc=deedsmis@aculink.net \
    --cc=linux-gcc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.