Re: gtkmm and gcc 4.0

[Chris Vine <chris cvine freeserve co uk>]

On Sunday 26 June 2005 11:45, John Taber wrote:
> My experiences trying out gcc 4.0 vs 3.3.5 with gtkmm 2.6.1
> 1) some dialog classes compile as 1/2 the size
> 2) most classes have the same nasty looking warning on shared libraries
> 3) linking has the warning that gtkmm wants to use libstdc++ so.5
> instead of libstdc++ so.6 (running gcc 4.0.1 Debian unstable)
> 4) one of my key programs segfaults with 4.0 - runs fine with 3.3.5
> (have not tracked down why yet)
>
> my initial conclusion: I've gone back to using 3.3.5 for now.  Maybe
> switch to 4.0 on next program version with gtkmm 2.8.  gcc 4.0 seems to
> have a big advantage on code size but since gtkmm relies on quite a few
> libraries, it might take a little while until all are pretty well
> compiled themselves under 4.0 and that all the latest versions are being
> used together (ie gtk just came out with 2.6.8, glib with 2.6.5 and I
> know I'm not using those yet).
>
> This also points out a real practical problem in maintaining a stable
> gtkmm version on a developer's machine when the underlying shared
> libraries keep updating and I have yet to see anywhere on the web site
> specific version numbers as to what is tested with what.

It looks as if in fact you have NOT recompiled gtkmm as you say, or if you 
have, it is not in a directory assessible to the loader.  gcc-3.3 uses 
version 5 of libstdc++, and gcc-3.4 and 4.0 use version 6.  In particular you 
would have encountered the same issue if you were to have changed your gcc 
version to 3.4.

If you do replace gcc-3.3 you will still need to keep its version 5 libstdc++ 
libraries somewhere in the /etc/ld.so.conf library directories because other 
programs may depend on them.  Versions 5 and 6 are parallel installable so 
your criticisms look off the mark.  Furthermore the information about 
versions was given to you and you did not need to search the web - it was in 
the warnings which you said you were given, which is why I am able to deduce 
what your problem is.  Ignoring "the same nasty looking warning on shared 
libraries" will not get you very far in any programming environment.

Chris