I don't know if this is real bug (as in ebuild), but I think issues like glibc/gcc upgrade should be clearly documented, so I suppose it's at least bug in documentation - I would expect I will find answer with steps I did. First: I looked in glibc-2.3.6.tar.bz2. Required version of gcc is still 3.2, both in configure and INSTALL file (in fact, 3.2 is recomended). So, why does ebuild need 3.4 ? Second: does it meen I need 3.4 only installed, or also selected ? Is it possible to select 3.2 (or 3.3.2-r5 in my case, to be exact) after emerging glibc ? Third: What problems will I have when I don't recompile every package as said in http://gentoo-wiki.com/HOWTO_Migrate_to_GCC_3.4 ? Must I reemerge system ? Note that I'm interested in answer both in case I don't unmerge gcc-3.3 and in case I do, but install some other package if possible (like libstdc++-v3).
Yes, it's really needed; too many bugs filed about issues caused by outdated gcc. http://www.gentoo.org/doc/en/gcc-upgrading.xml
Bugs with glibc, or bugs with unrelated packages ? Is it like when you put gtk-2.8 in firefox dependencies (see bug #135923) ? Can you answer my other questions ? Is it possible to run program which use both libstdc++ (one itself, one in library) ? I don't suppose so, but I don't want to spend whole week recompiling packages and solving bugs ... I personally didn't spot "obsolete gcc"-related problem yet.
(In reply to comment #2) > Bugs with glibc Bugs when compiling glibc. > Can you answer my other questions ? Bugzilla is for bugs, for questions there's IRC or forums.g.o. ;) > Is it possible to run program which use both libstdc++ (one itself, one in > library) ? I don't understand the above... > I don't want to spend whole week recompiling packages and solving bugs ... Read the gcc upgrading guide. > I personally didn't spot "obsolete gcc"-related problem yet. Bug 121501, Bug 129776, Bug 132122...
> > Can you answer my other questions ? > > Bugzilla is for bugs, for questions there's IRC or forums.g.o. ;) > Really ? :-( > > Is it possible to run program which use both libstdc++ (one itself, one in > > library) ? > > I don't understand the above... > Like when I have some game using new libstdc++ and SDL, which is using old libstdc++. > > I don't want to spend whole week recompiling packages and solving bugs ... > > Read the gcc upgrading guide. > I did. revdep-rebuild is still recompiling and it don't protect me from bugs either. At least I doubt no package will need to be upgraded to newer version. I have VERY old packages. > > I personally didn't spot "obsolete gcc"-related problem yet. > > Bug 121501, Bug 129776, Bug 132122... > At least I see I'm not the only one who prefer longer working compilers ...