Re: gtkmm and gcc 4.0

[John Taber <jtaber johntaber net>]

Thks for the info.  So, it sounds like my idea of waiting a bit before 
switching to 4.0 is a good one (unless one wants to do a lot of 
recompiling of gtkmm, dependencies, etc which in my case, I did not do 
and do not want to tackle right now).

As far as the dependencies go, I still think it is something that should 
be addressed. To some degree, Debian does this (it lists dependencies 
and goes thru somewhat a testing process, Ubuntu goes a step further by 
using a 6 mo cycle of packages somewhat tested to work together).  To me 
the best process would be to have a development "studio" or bundle so 
that every gtkmm version is tested with a known set of dependant 
libraries, ie gtkmm 2.8.0 might ship listed with gtk 2.8.1 and glib 
2.8.0 whatever.  Then if upgrades go wrong, there is a benchmark to fall 
back to.  In the current gtk 2.6.x series we have seen some changes go 
in, then get reverted out - did that affect the stability of gtkmm? 
Probably not, but it could.  Personally, that's the reason I would 
prefer static builds of gtkmm and our resulting programs, and though GPL 
licensing might be a problem, with disk space so cheap and available, 
who cares if the "studio" takes up 100 mb - let the compiler and program 
sort out only including what's needed.   Any agreement?

Roger Leigh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Chris Vine <chris cvine freeserve co uk> writes:
>
>
> > On Sunday 26 June 2005 12:15, Christian von Kietzell wrote:
> >
> > > Am Sonntag, den 26.06.2005, 04:45 -0600 schrieb John Taber:
> > >
> > > > 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)
> > >
> > > Some problems are to be expected. In order to use GCC 4.0 all C++
> > > libraries will have to be compiled using GCC 4.0, as 4.0 and 3.3.x are
> > > using different ABI versions. Debian hasn't made the transition yet.
> >
> > Are you sure about this?  They use different libstdc++ libraries but my 
> > understanding was the the C++ ABI was not broken between
> > gcc-3.3/3.4/4.0.
>
>
> Changing libstdc++ does break the ABI.  Debian is currently using GCC
> 3.3 with libstdc++5.  We will, in a few weeks, switch to GCC 4.0 and
> libstdc++6.  At this point all the C++ libraries will need to be
> rebuilt, and these problems will go away.  It's not possible to use
> multiple versions of libstdc++ in one program, so linking a library
> built against libstdc++5 with a program built with GCC 4.x is going to
> be dodgy.
>
>
> Regards,
> Roger
>
> - -- 
> Roger Leigh
>                 Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
>                 Debian GNU/Linux        http://www.debian.org/
>                 GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
>
> iD8DBQFCvp/UVcFcaSW/uEgRAjVhAKDvfK8/Hn4UzPHt+LkUQUIfBYGE/ACgyHyC
> peeQhT6i+EwLwb7VXJ8Xt3Q=
> =OLKb
> -----END PGP SIGNATURE-----
> _______________________________________________
> gtkmm-list mailing list
> gtkmm-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtkmm-list