[gentoo-user] Upgrading GCC (just to be sure)...

[gentoo-user] Upgrading GCC (just to be sure)...

[Jarry]

Hi,

today after syncing I found new version of GCC being available,
"emerge --pretend --update --deep --newuse world" shows:

[ebuild  NS   ] sys-devel/gcc-4.3.2-r3 [4.1.2] USE="..."

I found a "Gentoo GCC Upgrade Guide", but it deals with GCC 3.x,
or 3.x->4.x. Should I follow that guide when upgrading 4.x version
of GCC too? In a summary, the upgrade guide recommends this way:

# emerge -uav gcc
# gcc-config x86_64-pc-linux-gnu-4.3.2-r3
# env-update && source /etc/profile
# emerge --oneshot -av libtool
# emerge -eav system
# emerge -eav world
# emerge -aC =sys-devel/gcc-4.1.2

I'm asking just to be sure, because I have such a bad feeling,
that screwing up gcc upgrade might render my system unusable...

Jarry


-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] Upgrading GCC (just to be sure)...

[Albert Hopkins]

On Mon, 2009-03-30 at 19:56 +0200, Jarry wrote:
> Hi,
> 
> today after syncing I found new version of GCC being available,
> "emerge --pretend --update --deep --newuse world" shows:
> 
> [ebuild  NS   ] sys-devel/gcc-4.3.2-r3 [4.1.2] USE="..."
> 
> I found a "Gentoo GCC Upgrade Guide", but it deals with GCC 3.x,
> or 3.x->4.x. Should I follow that guide when upgrading 4.x version
> of GCC too? In a summary, the upgrade guide recommends this way:
> 
> # emerge -uav gcc
> # gcc-config x86_64-pc-linux-gnu-4.3.2-r3
> # env-update && source /etc/profile
> # emerge --oneshot -av libtool
> # emerge -eav system
> # emerge -eav world
> # emerge -aC =sys-devel/gcc-4.1.2
> 
> I'm asking just to be sure, because I have such a bad feeling,
> that screwing up gcc upgrade might render my system unusable...

You're going from a 4.x to a 4.x... it's a relatively minor upgrade, not
like going from 3.x to 4.x.  If you're that paranoid, keep 4.1.2 around
or create a quickpkg until they drop.

Re: [gentoo-user] Upgrading GCC (just to be sure)...

[Florian Philipp]

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

Jarry schrieb:
> Hi,
> 
> today after syncing I found new version of GCC being available,
> "emerge --pretend --update --deep --newuse world" shows:
> 
> [ebuild  NS   ] sys-devel/gcc-4.3.2-r3 [4.1.2] USE="..."
> 
> I found a "Gentoo GCC Upgrade Guide", but it deals with GCC 3.x,
> or 3.x->4.x. Should I follow that guide when upgrading 4.x version
> of GCC too? In a summary, the upgrade guide recommends this way:
> 
> # emerge -uav gcc
> # gcc-config x86_64-pc-linux-gnu-4.3.2-r3
> # env-update && source /etc/profile
> # emerge --oneshot -av libtool
> # emerge -eav system
> # emerge -eav world
> # emerge -aC =sys-devel/gcc-4.1.2
> 
> I'm asking just to be sure, because I have such a bad feeling,
> that screwing up gcc upgrade might render my system unusable...
> 
> Jarry
> 
> 

You don't need to follow this guide. Just emerge and you'll be fine.
However, you might want to make adjustments to CFLAGS (especially when
you have a newer CPU, there are new -march settings for your chip) and
reemerge cpu-intensive programs and maybe important libraries like glibc
to profit from the new features.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]

Re: [gentoo-user] Upgrading GCC (just to be sure)...

[KH]

Florian Philipp schrieb:
> Jarry schrieb:
>   
>> Hi,
>>
>> today after syncing I found new version of GCC being available,
>> "emerge --pretend --update --deep --newuse world" shows:
>>
>> [ebuild  NS   ] sys-devel/gcc-4.3.2-r3 [4.1.2] USE="..."
>>
>> [snip]
>>
>> Jarry
>>
>>
>>     
>
> You don't need to follow this guide. Just emerge and you'll be fine.
> However, you might want to make adjustments to CFLAGS (especially when
> you have a newer CPU, there are new -march settings for your chip) and
> reemerge cpu-intensive programs and maybe important libraries like glibc
> to profit from the new features.
>
>   
Hi,

have a look at: http://en.gentoo-wiki.com/wiki/Safe_Cflags#-march.3Dnative

I just changed this and did only follow up till emerge -eav system. Will
skip world unless I do run in trouble.

kh

Re: [gentoo-user] Upgrading GCC (just to be sure)...

[Maximilian Bräutigam]

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
-- 
Maximilian Bräutigam
max-braeu@gmx.de
www.chemie.uni-jena.de/jcf

[gentoo-user] Re: Upgrading GCC (just to be sure)...

[ABCD]

-----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-----

Re: [gentoo-user] Upgrading GCC (just to be sure)...

[KH]

Maximilian Bräutigam schrieb:
> 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
>   
Hi
I would try to run gcc-config -l and than change acording to the list
you get. Than run -c again.
kh

Re: [gentoo-user] Upgrading GCC (just to be sure)...

[Jarry]

Maximilian Bräutigam wrote:
> 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

At the end of GCC upgrade, I got these messages:
__________________________________________________
* The current gcc config appears valid, so it will not be
* automatically switched for you. If you would like to
* switch to the newly installed gcc version, do the following

* gcc-config x86_64-pc-linux-gnu-4.3.2
* source /etc/profile

* No profile selected, unable to utilize --use-old

* If you have issues with packages unable to locate libstdc++.la,
* then try running 'fix_libtool_files.sh' on the old gcc versions.

 >>> Recording sys-devel/gcc in "world" favorites file...

* Messages for package sys-devel/gcc-4.3.2-r3:
* If you have issues with packages unable to locate libstdc++.la,
* then try running 'fix_libtool_files.sh' on the old gcc versions.
 >>> Auto-cleaning packages...
 >>> No outdated packages were found on your system.

  * GNU info directory index is up-to-date.
________________________________________________________


So I just followed it, and everything went smooth so far...

Jarry


-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] Upgrading GCC (just to be sure)...

[Daniel Pielmeier]

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

Jarry schrieb am 30.03.2009 19:56:
> Hi,
> 
> today after syncing I found new version of GCC being available,
> "emerge --pretend --update --deep --newuse world" shows:
> 
> [ebuild  NS   ] sys-devel/gcc-4.3.2-r3 [4.1.2] USE="..."
> 
> I found a "Gentoo GCC Upgrade Guide", but it deals with GCC 3.x,
> or 3.x->4.x. Should I follow that guide when upgrading 4.x version
> of GCC too? In a summary, the upgrade guide recommends this way:
> 
> # emerge -uav gcc
> # gcc-config x86_64-pc-linux-gnu-4.3.2-r3
> # env-update && source /etc/profile
> # emerge --oneshot -av libtool
> # emerge -eav system
> # emerge -eav world
> # emerge -aC =sys-devel/gcc-4.1.2
> 
> I'm asking just to be sure, because I have such a bad feeling,
> that screwing up gcc upgrade might render my system unusable...
> 
> Jarry
> 
> 

The recommendations in the section "General Upgrade Instructions" should
apply here.

Another thing probably worth to mention is that some big packages (xorg,
mono, firefox, etc) are about to go stable in the near future. So it is
maybe a good idea to upgrade this packages in one go with the gcc
upgrade to avoid needlessly double compilation.

-- 
Daniel Pielmeier


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]