Using /usr/portage/profiles/hardened/x86 as profile. Notice that /usr/portage/profiles/hardened/package.mask contains =sys-devel/gcc-4.3.2* and =sys-devel/gcc-4.3.3, without an asterisk after 4.3.3. In this way, using this can cause emerge gcc-4.3.3-r2 while using ~x86 Reproducible: Always Expected Results: Really no version 4 of gcc can be emerged before officially unmasked.
It's not a bug. gcc-4.3.3-r2 is experimental on hardened profile with default enforcement of relro, bind now, pic/pie, fortify_source and -fno-strict-overflow. SSP has not been integrated yet.
Sorry to keep on asking for more information. You said that gcc-4.3.3-r2 do not integrate SSP implementation. So if I want to experience gcc:4's SSP, I can only emerge gcc-4.3.2? And is it recommended to test the gcc-4 SSP on non-critical hardened system, like some nut people' laptops? Is it currently really helpful for official work?
(In reply to comment #2) > Sorry to keep on asking for more information. You said that gcc-4.3.3-r2 do not > integrate SSP implementation. So if I want to experience gcc:4's SSP, I can > only emerge gcc-4.3.2? No, none of the gcc-4 implementations do SSP by default like hardened gcc-3.4.6 does. > > And is it recommended to test the gcc-4 SSP on non-critical hardened system, > like some nut people' laptops? Is it currently really helpful for official > work? > Well yeah.. it's testing/unstable marked right? So test on non-critical before deploying anywhere else of course. Yes, it's helpful... if people report successes or bugs they find.
