From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: nnir and swish++?
Date: 21 Jun 2001 11:15:36 -0400 [thread overview]
Message-ID: <vxkelsdzwx3.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <8766dp28ps.fsf@mclinux.com> (Josh Huber's message of "21 Jun 2001 10:44:47 -0400")
Josh Huber <huber@alum.wpi.edu> writes:
> I'm not sure what's gong on here, but it sounds like STL problems
> perhaps? I didn't have a problem building under debian unstable...
It turns out that there's an updated release, 5.0.1, which contains
this observation in Changes:
| 5.0.1
| *******************************************************************************
|
| BUG FIXES
| ---------
|
| * This releases fixes a lot of compile issues (mostly namespaces) with g++ 3.0.
|
| (This bug fix shall be known as bug fix GCC3.)
|
| * The changes to fix the above have apparantly caused bugs in (at least) g++
| 2.95.3 to manifest themselves:
|
| 1. In some cases, the compiler "forgets" that operator<<(
| ostream&, string const& ) has been defined. The hack
| workaround is to use operator<<( ostream&, char const* ) and
| use string::c_str().
|
| 2. The compiler "forgets" that stream manipulators have been defined.
| The workaround is not to use them. :-(
|
| (This fix shall be known as fix OOS.)
A quick attempt at a build of 5.0.1 gave me the same problem, so I'll
have to try to figure out what this means this evening -- I don't have
time to hack on it right now.
next prev parent reply other threads:[~2001-06-21 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 21:31 Josh Huber
2001-06-21 7:47 ` Marco Lonsing
2001-06-21 14:06 ` Karl Kleinpaste
2001-06-21 14:44 ` Josh Huber
2001-06-21 15:15 ` Karl Kleinpaste [this message]
2001-06-21 18:46 ` Wes Hardaker
2001-06-22 10:00 ` Kai Großjohann
2001-06-22 13:59 ` Josh Huber
2002-10-21 3:50 ` Christoph Conrad
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=vxkelsdzwx3.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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 NNTP newsgroup(s).