From: <llewelly@dbritsch.dsl.xmission.com>
To: Avi Green <avi-nospam@sputnik7.com>
Cc: Benjamin Kosnik <bkoz@cygnus.com>,
libstdc++-v3 Development List <libstdc++@sourceware.cygnus.com>,
GCC Installation Help List <gcc-help@gcc.gnu.org>
Subject: Re: Case history: Installing libstdc++ on i686-pc-linux-gnu (RedHat)
Date: Mon, 27 Mar 2000 21:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0003272229370.25409-100000@dbritsch.dsl.xmission.com> (raw)
In-Reply-To: <38DFE709.D9B51CBC@sputnik7.com>
On Mon, 27 Mar 2000, Avi Green wrote:
[snip]
> plus v3. A simple hello.cpp program generates the following on compile:
>
> $ g++ -I/usr/libstdc++-2.90.8/include/g++-v3 -L/usr/libstdc++-2.90.8/lib
I believe you need to add '-fhonor-std' to your command line.
By default, libstdc++-v3 builds with namespace std enabled; that is,
-fhonor-std .
However, for backwards compatiblity reasons, g++ treats namespace std as
the global namespace by default.
So if you use 'std::cout' in your code, g++ will generate a reference to
'cout' ... but libstdc++-v3 contains 'std::cout' , *not* 'cout' .
> Hello.cpp
> /tmp/cc2CbfSP.o: In function `main':
> /tmp/cc2CbfSP.o(.text+0x26): undefined reference to `cout'
[big long fat snip, including error message and a second question I
cannot answer.]
WARNING: multiple messages have this Message-ID
From: <llewelly@dbritsch.dsl.xmission.com>
To: Avi Green <avi-nospam@sputnik7.com>
Cc: Benjamin Kosnik <bkoz@cygnus.com>,
libstdc++-v3 Development List <libstdc++@sourceware.cygnus.com>,
GCC Installation Help List <gcc-help@gcc.gnu.org>
Subject: Re: Case history: Installing libstdc++ on i686-pc-linux-gnu (RedHat)
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0003272229370.25409-100000@dbritsch.dsl.xmission.com> (raw)
Message-ID: <20000401000000.TTfoU9E8SgQ5NO7n9RtdCtnErPla9CzOLnWQXTZ8GIE@z> (raw)
In-Reply-To: <38DFE709.D9B51CBC@sputnik7.com>
On Mon, 27 Mar 2000, Avi Green wrote:
[snip]
> plus v3. A simple hello.cpp program generates the following on compile:
>
> $ g++ -I/usr/libstdc++-2.90.8/include/g++-v3 -L/usr/libstdc++-2.90.8/lib
I believe you need to add '-fhonor-std' to your command line.
By default, libstdc++-v3 builds with namespace std enabled; that is,
-fhonor-std .
However, for backwards compatiblity reasons, g++ treats namespace std as
the global namespace by default.
So if you use 'std::cout' in your code, g++ will generate a reference to
'cout' ... but libstdc++-v3 contains 'std::cout' , *not* 'cout' .
> Hello.cpp
> /tmp/cc2CbfSP.o: In function `main':
> /tmp/cc2CbfSP.o(.text+0x26): undefined reference to `cout'
[big long fat snip, including error message and a second question I
cannot answer.]
next prev parent reply other threads:[~2000-03-27 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.3.91.1000327114055.13734A-100000@cse.cygnus.com>
2000-03-27 14:52 ` Case history: Installing libstdc++ on i686-pc-linux-gnu (Red Hat) Avi Green
2000-03-27 21:34 ` llewelly [this message]
2000-04-01 0:00 ` Case history: Installing libstdc++ on i686-pc-linux-gnu (RedHat) llewelly
2000-03-28 12:44 ` Case history: Installing libstdc++ on i686-pc-linux-gnu (Red Hat) Alexandre Oliva
2000-03-28 23:30 ` Avi Green
2000-03-29 12:14 ` Avi Green
2000-04-01 0:00 ` Avi Green
2000-04-01 0:00 ` Avi Green
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Avi Green
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.0003272229370.25409-100000@dbritsch.dsl.xmission.com \
--to=llewelly@dbritsch.dsl.xmission.com \
--cc=avi-nospam@sputnik7.com \
--cc=bkoz@cygnus.com \
--cc=gcc-help@gcc.gnu.org \
--cc=libstdc++@sourceware.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).