Upgrading your system to gcc 3.4(.4)

[Akaihiryuu]

That's really odd...emerge -e world for me definitely recompiled everything. Maybe your world file got messed somehow? Try running emaint --check world. On a side note, I followed the "slower" upgrade path...the one that involved emerge -e system ; emerge -e world, did it on 3 systems with no problems. However, it turns out that with gcc-3.4.4 and a c3-2 architecture, alsa-driver won't compile (not even the latest ~x86 version). It only happens when the toolchain has been compiled with -march=c3-2...at least k6-3 and athlon-xp work. This does not indicate a problem with the gcc upgrade, it apparently happens on all c3-2 machines using gcc-3.4.4. A bug report has been filed: https://bugs.gentoo.org/show_bug.cgi?id=117801

[Buddha001]

Well, I went in and manually added some packages to my world file that I know I have installed, but even then it only gets to about 569 packages out of some 700 I believe I have installed (as per Kuroo). Also, does one need to recompile the kernel after doing this whole thing? Beginning to wonder if it was really worth it or not...

[Akaihiryuu]

I recompiled my kernel...I'm not 100% sure if it's necessary or not, but I do know that gcc 3.4 is not binary compatible with gcc 3.3, so if everything isn't recompiled some things are going to break.

[acfreeman]

Hi all,

I'm having some problems with emerge -e system on gcc-3.4
I tried to upgrade my system from 3.3 by the following method:

[rickj]

I just started an upgrade on a system which was installed with 2005.1. Apparently it installed a 386 version of the compiler, because after emerging the compiler and running gcc-config I see:

[yaneurabeya]

rickj:
The CHOST variable attached to the compiler does not matter. Just make sure to select the full string for your new compiler with gcc-config, and you *should* be fine, ie

[yaneurabeya]

[rickj]

Thanks yaneurabeya, what I actually did after the emerge was:

[eyeL]

after you set your gcc to use that one, why don't you just

emerge -P gcc, to get rid of the stuff you aren't using?
_________________
[theNPA - down for updates] | [Adopt an unanswered post]
gentoo 2005.1 [lazy] - gcc 4.1.1

[rickj]

Well, at the moment I can't emerge at all, so the question hardly arises....

At present all my stuff is compiled with the previous compiler, so I would suspect it should link to its own libraries. I would not expect to be able to remove the old compiler until everything has been recompiled, and indeed that's the order the upgrade guide suggests.

I suspect the answer may lie in

https://forums.gentoo.org/viewtopic.php?t=145439

so I'll try it this evening, when I'm back at the system in question.

[rickj]

The above post does not seem to help. The famous one-liner does not work in this case, because the libraries have moved from:

[jvprat]

Hello,

I've got a problem since I updated to gcc-3.4. At first I didn't follow the migration guide strictly. After solving some other issues, I'm now trying to follow the migration guide, but I can't even do "emerge -e system", since some packages like aspell, ffmpeg and xorg-x11 fail to build. I hope I can still fix it

For example, this is what I get when I try to emerge aspell:

[yaneurabeya]

[jvprat]

Hi again,

I just had to ask it on the forums to find the answer myself

I found this:

[rickj]

Now I'm even more confused. I emerged the new gcc, but did not uninstall the old one. My impression was that both now existed on the system. In fact, the message at the end of the gcc-3.4.4 emerge specifically stated that the present gcc configuration seemed valid, and would not be changed; it advised the use of gcc-config to change to the new compiler. The upgrade guide seems to recommend that the old gcc should not be removed until everything has been recompiled using the new one. Does this constitute a slotted setup? If not, how do I build one?

I tried the fix of merely changng back to gcc-3.3.6 using gcc-config, and that appeared to succeed, at least as far as gcc-config -l was concerned, but my python was still dead, still unable to find its library.

A gentoo system without python is remarkably impaired. I suspect I could fix the linkages with python-updater, but of course it's a python script.

[yaneurabeya]

I just use slots for multiple compilers so all the libs and junk remain in tact even after I emerge a different version of gcc. But, in this case the slotting would allow you to have multiple compilers, and then would have allowed you enough time and testing to determine whether or not unmerging the old version was really a wise idea.

[rickj]

Well, I seem to have squirmed out of the trap.

env-update, a python script, was dead, but I was still able to hand-edit /etc/ld.so.conf
(which one should never normally do) and add the old libraries:

[tld]

Question: I was trying to remember if I had any packages other than the sun java that need to be downloaded manually. Is ther any way I can determine this ahead of time? I don't want to have things barf part way through.

Tom

[acfreeman]

[thomasvk]

[acfreeman]

[thomasvk]

locate searches in some kind of index rather than on the filesystem. Have you ran 'updatedb' to create the search index? If you want to search on the file system use 'find' ('find -iname libstdc++.so.6' for example).

[acfreeman]

[tld]

[acfreeman]

I found out something else too. This "undefined references" problem comes for _certain_ c++ written packages. For example, there is no compiling failure for kdelibs, but giving warnings: