-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Maximilian Bräutigam wrote: > Hi all, > > it was said before: >> You don't need to follow this guide. Just emerge and you'll be fine. > > I would expect, that this is not the whole purpose. For example if I use > "eix gcc", I get two installed versions: 4.1.2 and 4.3.2-r3 > > "gcc -v" returns "gcc-Version 4.1.2 (Gentoo 4.1.2 p1.1)" > "gcc-config -c" returns "x86_64-pc-linux-gnu-4.1.2" > > So, obviously I am not using the new GCC compiler and being honest, I > made half a year ago the mistake to deinstall gcc without upgrading. I > configured a hole new system, because nothing worked anymore. > Due to the mentioned problems my question is, do I have to configure > # gcc-config x86_64-pc-linux-gnu-4.3.2 > ... or ... > # gcc-config x86_64-pc-linux-gnu-4.3.2-r3 > > kind regards, > der Max
IIRC, by default it will start using the new compiler, but the command is `gcc-config x86_64-pc-linux-gnu-4.3.2` (or even just `gcc-config 4.3.2`); for a list of compiler versions you currently have installed and can use with gcc-config, see the output of `gcc-config -l`. - -- ABCD -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknSDSgACgkQOypDUo0oQOqklACgprThXNNyLJRc5NH1nEoDQUQm 0tIAoNh1Dc7PaCzsD3panAfqwy0d3GGx =1WDl -----END PGP SIGNATURE-----
