From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36677 Path: main.gmane.org!not-for-mail From: Karl Kleinpaste Newsgroups: gmane.emacs.gnus.general Subject: Re: nnir and swish++? Date: 21 Jun 2001 11:15:36 -0400 Message-ID: References: <87elsealdo.fsf@mclinux.com> <8766dp28ps.fsf@mclinux.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172225 9885 80.91.224.250 (21 Oct 2002 03:50:25 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:50:25 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 19953 invoked from network); 21 Jun 2001 15:15:38 -0000 Original-Received: from mesquite.slip.cs.cmu.edu (HELO cinnamon.vanillaknot.com) (128.2.207.11) by gnus.org with SMTP; 21 Jun 2001 15:15:38 -0000 Original-Received: (from karl@localhost) by cinnamon.vanillaknot.com (8.11.2/8.11.2) id f5LFFaI04435; Thu, 21 Jun 2001 11:15:36 -0400 Original-To: ding@gnus.org X-Face: ?=p^Gj2JkX~UU_@W}[q/'Dxn19x-zfIQ](y<&ky/?1-&Nz&,!W}R.Gp+"LeGojoR =RF>?!XVs{a:`Yt(gqM<#$Zy(C@]'dR4Hy4S1.I(n3:2"R:=Uy!)K9>U!gNTyH{p +_w#F[gt).$Vyvo5=9LF^PeQ(@H#}QLAbfyYxX/8t:TDR5nA\|RmJO"EwjL8tWyvM In-Reply-To: <8766dp28ps.fsf@mclinux.com> (Josh Huber's message of "21 Jun 2001 10:44:47 -0400") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Developer-Friendly Unix APIs) Original-Lines: 33 Xref: main.gmane.org gmane.emacs.gnus.general:36677 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36677 Josh Huber 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.