Sven Köhler wrote:
Well, the problem here is that compiling some packages with one version
of GCC and others with another version of GCC (on the same system) is
asking for trouble. This means that ebuilds shouldn't change the GCC
version in use. If the user wants to try it and see if it works, let
them have at it, but don't do it automatically - it *will* eventually
break someone's system (maybe not with 3.4+4.0/4.1, but who knows with
future versions...remember the migration from GCC 3.3 to 3.4?).
then they stay broken ... add a warning to the ebuild if `gcc-major-version`
is "4" (see toolchain-funcs.eclass)
some software, like qemu and others, are simply not compatible with gcc
4.x and they will not become compatible due to severe conceptional issues.
Hmm, but ...
there is the possibility to have multiple gcc versions installed. So why
not set CC and/or CXX variables inside the ebuild, and then compile the
app with the "right" gcc-version?
At this point, it just bugs me, that gentoo is staying below its potential.
Well, hmmm, you might want to say, that there will be trouble because of
applications/libraries linked to different libstdc++ versions - or
I'm always willing to learn, but this really bugs me, because gentoo
really has potential for what's needed in this situation.
P.S. Who knows...eventually these incompatible packages might just make
the move to GCC 4 (possibly on a major update). Until they do, tho,
they'll just have to be broken (which is a shame...I like qemu).
firstname.lastname@example.org mailing list