public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: <llewelly@dbritsch.dsl.xmission.com>
To: Jennifer Okada <jokada@oceanit.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: undefined references
Date: Thu, 15 Jun 2000 14:35:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0006151425411.32182-100000@dbritsch.dsl.xmission.com> (raw)
In-Reply-To: <B56E6BDB.43%jokada@oceanit.com>

This question originially appeared on gcc-bugs; I am cc-ing to
  gcc-help as it seems more appropriate.

On Thu, 15 Jun 2000, Jennifer Okada wrote:

> Hi.  I'm not sure if this is the right place to ask this question but here
> goes.
> 
> I'm using version egcs -2.91.66 on Red Hat Linux.  I'm trying to compile a
> C++ program, but I'm getting errors about undefined references to 'cout' and
> 'ostream::operator << (int)'.  I included <iostream.h> so I don't know what
> the problem is.  

Without exact commandline and source code, I cannot tell what the problem
  is.

> Any ideas?  Thanks. 

(0) Compile c++ code with 'g++', and not 'gcc'; gcc will not link in
    libstdc++, g++ will.

(1) Do not use -fhonor-std unless you rebuilt your libstdc++ with
    -fhonor-std .

(2) Make sure libstdc++ is installed.


The above are wild guesses; they may or may not apply to you.


       reply	other threads:[~2000-06-15 14:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B56E6BDB.43%jokada@oceanit.com>
2000-06-15 14:35 ` llewelly [this message]
2004-04-27 11:43 gnuml
2004-04-27 12:16 ` Eljay Love-Jensen
2004-04-27 12:21 Lev Assinovsky
2007-12-01  1:26 Undefined References Michael Sullivan
2007-12-01  4:01 ` Tom Browder
2007-12-01  4:28   ` Michael Sullivan
2007-12-01  4:43     ` Tom Browder
2007-12-01 11:32       ` Michael Sullivan
2007-12-01 12:22         ` Tom Browder
2007-12-01 12:43           ` Michael Sullivan
2007-12-01 13:09             ` Tom Browder
2007-12-01 13:16               ` Michael Sullivan
2007-12-01 13:23                 ` Brian Dessent
2007-12-01 13:27                   ` Michael Sullivan
2007-12-01 14:22                     ` Tom Browder
2007-12-01 14:28                       ` Michael Sullivan
2007-12-01 14:45                         ` Tom Browder
2007-12-01 15:27                           ` Tom Browder
2007-12-01 15:34                             ` Michael Sullivan
2007-12-01 15:43                               ` Tom Browder
2007-12-01 15:44                                 ` Tom Browder
2007-12-01 15:49                                   ` Michael Sullivan
2007-12-01 16:01                                     ` Tom Browder
2007-12-02  2:59                                       ` Tom Browder
2007-12-01 17:45                                 ` Ted Byers
2007-12-01 13:29                   ` Tom Browder
2007-12-01 15:14 J.C. Pizarro
2007-12-01 15:30 ` Tom Browder

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.LNX.4.21.0006151425411.32182-100000@dbritsch.dsl.xmission.com \
    --to=llewelly@dbritsch.dsl.xmission.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jokada@oceanit.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).