libstdc++ is missing sstream or strstream classes...??

BroX · 05-13-2004, 10:47 AM

When configuring fluxbox-0.9.9 it ends with the following messages:

Code:

checking sstream usability... no
checking sstream presence... no
checking for sstream... no
checking strstream usability... no
checking strstream presence... no
checking for strstream... no
configure: error: Your libstdc++ doesn't have the sstream or strstream classes

What does this mean and what can I do o fix this? I have googled around and rtfm'd but it didn't shed any light.

[EDIT] I tried reinstalling/upgrading libstdc++, but it's unclear to me which files I actually need? Any help welcome!

Cheers, Leon.

leonscape · 05-13-2004, 05:52 PM

You need to upgrade GCC, I'd recommend 3.2 or 3.3 ( 3.4 requires a patch from the fluxbox site.

BroX · 05-14-2004, 01:48 AM

Thanx! If I remember correctly I tried that once, without success. And isn't there going to be a problem with stuff that was compiled with an earlier gcc-version?
Nice project for the weekend ;-)

If anyone has any tips how to upgrade gcc successfully I'd love to hear all about it!

Cheers, Leon.

BroX · 05-17-2004, 08:44 AM

Okay, upgrading gcc wasn't that difficult. Last time I tried to do it from source, but just getting the slackware package was a lot easier ;-) So I removed gcc 2.95 and upgraded to gcc 3.2.3.

But now when configuring fluxbox 0.9.9 there's loads of errors on header files. I'll paste parts of it below:

Code:

bash-2.05b# ./configure
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
/home/leon/rpms/fluxbox-0.9.9/missing: Unknown `--run' option
Try `/home/leon/rpms/fluxbox-0.9.9/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... no  <--- ???? isn't this weird?
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking for a BSD-compatible install... /usr/bin/ginstall -c

Then many times the following (for different *.h files):

Code:

checking for ANSI C header files... (cached) no
checking errno.h usability... no
checking errno.h presence... yes
configure: WARNING: errno.h: present but cannot be compiled
configure: WARNING: errno.h:     check for missing prerequisite headers?
configure: WARNING: errno.h: see the Autoconf documentation
configure: WARNING: errno.h:     section "Present But Cannot Be Compiled"
configure: WARNING: errno.h: proceeding with the preprocessor's result
configure: WARNING: errno.h: in the future, the compiler will take precedence
configure: WARNING:     ## ------------------------------------------ ##
configure: WARNING:     ## Report this to the AC_PACKAGE_NAME lists.  ##
configure: WARNING:     ## ------------------------------------------ ##
checking for errno.h... yes
checking ctype.h usability... no
checking ctype.h presence... yes
configure: WARNING: ctype.h: present but cannot be compiled
configure: WARNING: ctype.h:     check for missing prerequisite headers?
configure: WARNING: ctype.h: see the Autoconf documentation
configure: WARNING: ctype.h:     section "Present But Cannot Be Compiled"
configure: WARNING: ctype.h: proceeding with the preprocessor's result
configure: WARNING: ctype.h: in the future, the compiler will take precedence
configure: WARNING:     ## ------------------------------------------ ##
configure: WARNING:     ## Report this to the AC_PACKAGE_NAME lists.  ##
configure: WARNING:     ## ------------------------------------------ ##
checking for ctype.h... yes
checking dirent.h usability... no
checking dirent.h presence... yes
configure: WARNING: dirent.h: present but cannot be compiled

.....and so on....

And finally it ends with:

Code:

checking for sstream... yes
checking whether time.h and sys/time.h may both be included... no
checking for basename... no
checking for basename in -lgen... no
checking for getpid... no
checking for setlocale... no
checking for sigaction... no
checking for strcasestr... no
checking for snprintf... no
checking for vsnprintf... no
checking for catopen... no
checking for catgets... no
checking for catclose... no
checking for strftime... no
checking for t_open in -lnsl... no
checking for socket in -lsocket... no
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for gethostbyname... no
checking for gethostbyname in -lnsl... no
checking for gethostbyname in -lbsd... no
checking for connect... no
checking for connect in -lsocket... no
checking for remove... no
checking for remove in -lposix... no
checking for shmat... no
checking for shmat in -lipc... no
checking for IceConnectionNumber in -lICE... no
checking for XOpenDisplay in -lX11... no
configure: error: Could not find XOpenDisplay in -lX11.
bash-2.05b#

I have never encountered these errors, so somehow it has to do with upgrading gcc from 2.95.3 to 3.2.3. Can anyway point me in the right direction of how to correct this?

Cheers, Leon.

leonscape · 05-17-2004, 05:54 PM

make sure that there are either symlinks, or the files are called gcc, g++ etc.

type gcc -v

If you get command not found then thats your problem. you then ned to do this:

cd /usr/bin
ln -s gcc-3.2.3 gcc <--- ( The version number maybe diffrent check with ls gcc* )

and repeat this for g++, gbug, and gcov.

Also try updaing autoconf, and automake.

You seem to be missing header files for X11 download the development packages, the normal packages don't usually contain everthing you need to compile something against the libs.

BroX · 05-19-2004, 03:43 AM

gcc -v gave decent output.

However, after some mishaps I decided to do a fresh install, after which fluxbox 0.99 installed witout any problems (with gcc 3.2.3).

Cheers, Leon.