Re: [Bayonne-devel]Compile error on commoncpp2-1.0.0

[Jason Spence]

On Sun, Sep 08, 2002 at 05:29:07PM +0200, Federico Montesino Pouzols wrote: 
> On Sun, Sep 08, 2002 at 02:17:49AM -0700, Jason Spence wrote:
> > On Sun, Sep 08, 2002 at 05:23:49AM +0300, Vitaly wrote: 
> > > Hi,
> > > 
> > > I am having trouble compiling commoncpp2-1.0.0 on Red Hat 6.2 (Kernel
> > > 2.2.14-5.0).
> > > I get to a point where I receive the following error:
> > > 
> > > /bin/sh ../libtool --mode=compile
> > > c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY  
> > > -I/
> > > usr/local/include -D_GNU_SOURCE -I../include -c socket.cpp
> > > rm -f .libs/socket.lo
> > > c++ -DHAVE_CONFIG_H -I. -I. -I../include -I../src -DCCXX_EXPORT_LIBRARY 
> > > -I/u
> > > sr/local/include -D_GNU_SOURCE -I../include -c socket.cpp   -fPIC -DPIC -o
> > > .libs/socket.lo
> > > socket.cpp:51: sstream: No such file or directory
> > > make[1]: *** [socket.lo] Error 1
> > > make[1]: Leaving directory `/root/Work/commoncpp2-1.0.0/src'
> > > make: *** [all-recursive] Error 1
> > 
> > This is a bit different from the problem I'm having, but I do know
> > that the commoncpp2 build is currently broken in at least one other
> > way.  You must apply the attached patch to get it to work.  I've
> > already sent it to David for application.
> > 
> > Unfortunately, David is stuck in some third world country with spotty
> > Network access at the moment and hasn't seem to have applied it yet
> > (http://savannah.gnu.org/cgi-bin/viewcvs/commoncpp/commoncpp2/include/cc%2B%2B/)
> 
>       Hi, this is now fixed in CVS. My apologies, since I introduced
> this problem.
> 
>       However, this bug was introduced after 1.0.0 was released. The
> make errors above complain that the sstream header is missing. I see
> that Vitaly uses Red Hat 6.2, which probably comes with a gcc release
> older than 2.9x that does not have the newer sstream C++ header.
> 
>       We are using sstream to follow the newer C++ standard and gcc
> 3.x releases. Perhaps we will have to add some configuration stuff to
> keep compatibility with old systems.

Do you think you could put a warning in configure.in if the check for
sstream fails as well as instructions to the user on how to upgrade to
3.x if necessary?  I'm sure it would cut down on the "Common C++ is
broken" posts to the list :)

-- 
 - Jason

The bureaucracy is expanding to meet the needs of an expanding
bureaucracy.