RE: [ROOT] rootcint and ostringstream

From: Philippe Canal (
Date: Thu Oct 14 2004 - 21:38:46 MEST


The iostream CINT implementation used for gcc 2.96 is indeed typedefing
ostrstream to ostringstream.
Fixing the problem would requires to regenerate this layer (and possibility
having to modify some of the header file used in the process).


-----Original Message-----
From: []
On Behalf Of Alessandro Thea
Sent: Thursday, October 14, 2004 12:22 PM
To: roottalk
Subject: [ROOT] rootcint and ostringstream

Hi all,
I have a problem with dictionary generated by rootcint and ostringstream.
We have a class EsafMsg inheriting from ostringstream. It compiles well,
both source and rootcint dictionary, on RedHat 9, gcc 3.32 but when I mov to
RedHat 7.2 gcc 2.96 something strange happens.
rootcint misinterpret ostringstream and put in the dictionary "ostrstream"
instread of "ostringstream". g++ compiles EsafMsg, no errors, but when tries
to compile the dictionary complains because "ostrstream" is not defined.
The same error applies also to "stringstringbase" <--> "strstringbase"
I have to add that the linux boxes I'm trying to compile EsafMsg on are in
Lyon Computer Center and it's very likely that rootcint get fooled by some
local setting.
I've also checked the dictionary created on RH9 and there "ostringstream" is
used correctly.
My question is: there is a way to understand why or where rootcint decide to
use ostrstream instead of  ostringstream?



  Alessandro Thea
  Ph.D. Student
  Dipartimento di Fisica dell'Universita' di Genova and
  Istituto Nazionale di Fisica Nucleare, Sezione di Genova,
  Via Dodecaneso 33, I-16146, Genova, Italia.
  Tel: +39 010 3536468               E-Mail: 

This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:10 MET