On Wed, 12 Aug 2015 05:18:54 -0400, covici wrote: > Holger Hoffstätte wrote: > >> On Tue, 11 Aug 2015 12:01:50 +0200, Helmut Jarausch wrote: >> >> > On 08/10/2015 05:29:04 PM, James wrote: >> >> Hello, >> >> >> >> Just for grins, I'm thinking about installing a gentoo system that >> >> is (~) testing and newer codes and setting gcc-.5.2 as the default >> >> compiler. Anyone doing this yet? Will it mostly work or should I >> >> wait? Workstation with lxqt-0.9x. >> > >> > I don't use lxqt here, but ... >> > I'm using gcc-5.2.0 very successfully here. I am not aware of a >> > single package which doesn't compile with this version. >> > And the kernel itself compiles just fine (currentlich running >> > 4.2.0-rc6 compiled with gcc-5.2.0) >> >> +1 >> >> I just updated all my ~amd64 multilib systems to 5.2 and everything >> still works without a hitch, including acroread & skype. 4.9.3 is gone. >> :) >> >> > One caveat though when upgrading a system which has been built with >> > gcc-x for x < 5. >> > The (pure) C++ libraries aren't compatible with older versions so >> > that all packages which link to libstdc++ or libsupc++ have to be >> > rebuilt. Packages which just use C aren't effected at all. >> >> Interestingly I didn't have to rebuild anything (yet), which I find >> surprising given the changes in the ABI and std::string. I expected at >> least a few problems, >> but so far - nothing. > > I can't even emerge gcc-5.2.0 because of missing keyword, as of a sync > of yesterday, so what is happening with that?
The ebuild currently doesn't have any keywords, so enable them: $grep gcc /etc/portage/profile/package.accept_keywords >=sys-devel/gcc-5.2.0 ** (or your specific arch instead of **) Enjoy. :) -h
