| 1 |
On 4/6/2010 6:40 AM, Kraus Philipp wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I run in a virtual machine a gentoo (~x86) system. I synced the portage |
| 5 |
> tree at the weekend an run emerge --update |
| 6 |
> |
| 7 |
> The update runs without errors, but emerge installed the gcc 4.3.4, |
| 8 |
> but on the system is the 4.4.3 installed |
| 9 |
> |
| 10 |
> [ebuild NS ] sys-devel/gcc-4.3.4 [4.4.3] USE="hardened mudflap nls |
| 11 |
> nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -fortran |
| 12 |
> -gcj -gtk (-libffi) (-multilib) -multislot (-n32) (-n64) -nocxx -nopie |
| 13 |
> -objc -objc++ -objc-gc -test -vanilla" |
| 14 |
|
| 15 |
You have the +hardened USE flag set. Did you just recently switch to |
| 16 |
the hardened profile? If so, make sure you followed the upgrade guide |
| 17 |
for hardened profiles, which should have warned you what was going to |
| 18 |
happen here. |
| 19 |
|
| 20 |
In the base system, gcc-4.4 is still masked off for hardened users |
| 21 |
because it's not quite ready for production use. If you want to use gcc |
| 22 |
4.4 and all it's hardened features, you need to do two things: |
| 23 |
|
| 24 |
1. Add the hardened-development overlay, for example using layman: |
| 25 |
|
| 26 |
basement ~ # layman -a hardened-development |
| 27 |
|
| 28 |
2. Unmask gcc-4.4: |
| 29 |
|
| 30 |
basement ~ # mkdir /etc/portage/package.unmask |
| 31 |
basement ~ # echo '=sys-devel/gcc-4.4*' >> |
| 32 |
/etc/portage/package.unmask/hardened |
| 33 |
|
| 34 |
After that, you should get gcc 4.4.3 back. |
Archives