>> Steve Langasek <vorlon@netexpress.net> writes:
> We should count ourselves lucky that we don't have stable releases using
> each of the GCC 2.9x, 3.0, and 3.1 ABIs.
Does anyone have thoughts on a Debian-wide migration towards GCC 3.2?
(Or, for that matter, towards *anything* in the 3.x line). g++ 3.2 is
a superb compiler, much more standards conformant, less bugs and all
arround something you'd like to have. The problem is that all our C++
libraries are compiled using 2.95.x (on i386 at least) and that
precludes using g++ 3.2 for development. To make things more
interesting, some people are already releasing code which makes 2.95.4
choke.
Uhm... I'm extremely confused now... I wanted to count the number of
affected packages, but then I noticed:
$ dpkg -s libgtkmm1.3-11 | grep ^Depends
Depends: libatk1.0-0 (>= 1.0.2), libc6 (>= 2.2.4-4), libglib2.0-0 (>= 2.0.4), libgtk2.0-0 (>= 2.0.5), libpango1.0-0 (>= 1.0.3), libsigc++-1.1-4
My guess is that that's a C++ library being linked with gcc instead of
g++.
Ignoring that for the moment, I have:
$ grep-available -s Package -F Depends libstdc++ | wc -l
823
So, we are talking about 1000 packages, give or take a hundred.
--
Marcelo