View previous topic :: View next topic |
Author |
Message |
holymacaroni n00b
Joined: 06 Mar 2003 Posts: 63
|
Posted: Fri Jul 18, 2003 3:31 am Post subject: Safely Updating glibc, gcc, binutils? |
|
|
ok, i did an emerge rsync tonight and an emerge -up world and it seems that new versions of glibc, gcc, and binutils are available.
Code: | Calculating world dependencies ...done!
[ebuild U ] sys-devel/gcc-config-1.3.3-r1 [1.3.1-r1]
[ebuild U ] sys-devel/gcc-3.2.3-r1 [3.2.2]
[ebuild U ] sys-libs/glibc-2.3.2-r1 [2.3.1-r4]
[ebuild U ] sys-devel/binutils-2.14.90.0.2 [2.13.90.0.18] |
i know these aren't just any packages, so i'm wondering if there is anything special i have to do. i was planning on doing an emerge -u world then emerge -e world to update my installed packages to work with the updates, but i'm not sure if that's everything. any suggestions would be great, thanks. |
|
Back to top |
|
|
zhenlin Veteran
Joined: 09 Nov 2002 Posts: 1361
|
Posted: Fri Jul 18, 2003 5:38 am Post subject: |
|
|
Do in this order:
glibc binutils gcc-config gcc glibc
Yes, you compile glibc twice. This is so that any bugs in the previous compiler the don't affect the glibc and any bugs in the previous glibc don't affect the new compiler. |
|
Back to top |
|
|
holymacaroni n00b
Joined: 06 Mar 2003 Posts: 63
|
Posted: Sat Jul 19, 2003 8:29 am Post subject: |
|
|
ok, i've been looking for definitive instructions on how to safely do this and unfortunately i can't afford to experiment. thanks for replying. so i..
Code: | emerge -u glibc && emerge -u binutils && emerge -u gcc-config && emerge -u gcc |
then i just unmerge and reemerge glibc? sorry for being so picky, but i really can't afford to have something go wrong on this box. what about running emerge -e world when i'm finished? again, thanks. |
|
Back to top |
|
|
hensan l33t
Joined: 26 Jun 2003 Posts: 868 Location: Sweden
|
Posted: Sat Jul 19, 2003 11:44 am Post subject: |
|
|
First of all, unmerging glibc is a Bad Idea(tm), without it you can't compile anything, including a new version of glibc. Practically everything on you system relies on the glibc libraries and will stop working without them.
Second, 'emerge -u glibc' (in this case) also emerges the new versions of gcc, gcc-config and binutils, so all those -u:s won't work.
So the line should look like this:
Code: | emerge -u glibc && emerge binutils && emerge gcc-config && emerge gcc && emerge glibc |
|
|
Back to top |
|
|
dabooty Guru
Joined: 15 May 2003 Posts: 482 Location: Belgium
|
Posted: Sat Jul 19, 2003 5:32 pm Post subject: |
|
|
should the whole system be rebuillded afterwards, or should it continue working and compiling new packages just like that? _________________ registered user #284425
get yourself counted
http://counter.li.org
------
#emerge -pv solves a lot of questions beforehand |
|
Back to top |
|
|
hensan l33t
Joined: 26 Jun 2003 Posts: 868 Location: Sweden
|
Posted: Sat Jul 19, 2003 6:22 pm Post subject: |
|
|
No, there's no need to recompile everything. Personally, I didn't even bother with the re-emerging of glibc. |
|
Back to top |
|
|
m0sk n00b
Joined: 18 Apr 2003 Posts: 39 Location: Belgium
|
Posted: Sat Jul 19, 2003 6:55 pm Post subject: |
|
|
dabooty wrote: | should the whole system be rebuillded afterwards, or should it continue working and compiling new packages just like that? |
Nope, there's no benefit in rebuilding everyting as far as I'm aware. The new gcc is just a bugfix release, so unless you were previously having issues with something due to some gcc bug, there's no need to recompile all the stuff.
That said, the merge of glibc/gcc/binutils went just fine for me. |
|
Back to top |
|
|
zhenlin Veteran
Joined: 09 Nov 2002 Posts: 1361
|
Posted: Sun Jul 20, 2003 3:21 am Post subject: |
|
|
I use march=pentium4
Rebuilding glibc allowed me to use unmodified CFLAGS without getting the floating-point error. |
|
Back to top |
|
|
dmolavi Apprentice
Joined: 24 Feb 2003 Posts: 153 Location: Washington Township, NJ
|
Posted: Sun Jul 20, 2003 8:54 pm Post subject: |
|
|
damn, how long does this take? i'm running a VIA C3 800MHz, and it's in the middle of gcc after 5+ hours.... |
|
Back to top |
|
|
timfreeman Tux's lil' helper
Joined: 19 May 2003 Posts: 142 Location: Chicago
|
Posted: Mon Jul 21, 2003 3:59 am Post subject: portage or glibc first? |
|
|
Following hensan's code, the first part, emerge -u glibc, has this:
Code: | [ebuild U ] dev-lang/python-2.2.3-r1 [2.2.2]
[ebuild U ] sys-apps/portage-2.0.48-r5 [2.0.48-r1]
*** Portage will stop merging at this point and reload itself,
recalculate dependencies, and complete the merge.
[ebuild U ] sys-devel/gettext-0.11.5-r1 [0.11.5]
[ebuild U ] sys-devel/binutils-2.14.90.0.2 [2.13.90.0.18]
[ebuild U ] sys-devel/gcc-3.2.3-r1 [3.2.2]
[ebuild U ] sys-libs/glibc-2.3.2-r1 [2.3.1-r4] |
and then the other commands:
Code: | [ebuild U ] sys-devel/binutils-2.14.90.0.2 [2.13.90.0.18]
[ebuild R ] sys-devel/gcc-config-1.3.3-r1
[ebuild U ] sys-devel/gcc-3.2.3-r1 [3.2.2]
[ebuild U ] sys-libs/glibc-2.3.2-r1 [2.3.1-r4] |
Should I leave out the -u ? Because the binutils, gcc, and glibc are all getting compiled twice. It only makes sense to me to compile the compiler twice .. ?
If I do leave the -u out, then I of course get the straight:
Code: |
[ebuild U ] sys-libs/glibc-2.3.2-r1 [2.3.1-r4]
[ebuild U ] sys-devel/binutils-2.14.90.0.2 [2.13.90.0.18]
[ebuild R ] sys-devel/gcc-config-1.3.3-r1
[ebuild U ] sys-devel/gcc-3.2.3-r1 [3.2.2]
[ebuild U ] sys-libs/glibc-2.3.2-r1 [2.3.1-r4] |
Another thing:
Also, as you can see above, this way has portage and pythong being built first.. But if you emerge -up portage at this same point (and I imagine a lot of people are in my same place at the moment today), it has this:
Code: | [ebuild U ] sys-devel/gettext-0.11.5-r1 [0.11.5]
[ebuild U ] sys-devel/binutils-2.14.90.0.2 [2.13.90.0.18]
[ebuild U ] sys-devel/gcc-3.2.3-r1 [3.2.2]
[ebuild U ] sys-libs/glibc-2.3.2-r1 [2.3.1-r4]
[ebuild U ] dev-lang/python-2.2.3-r1 [2.2.2]
[ebuild U ] sys-apps/portage-2.0.48-r5 [2.0.48-r1] |
that is, it compiles portage with the newer version of gcc... but the -up glibc has it compiling the new python and portage beforehand..
Any suggestions? I personally would rather compile python and portage with the bug-updated toolchain.
Any suggestions? |
|
Back to top |
|
|
|