Updating glibc gentoo
The easiest way to achieve that is by rebooting the machine after updating the sys-libs/glibc package.Note: Should you run into compilation failures while updating, please see bug 574948.* =glibc-2.12 #362315 * The ebuild phase 'compile' with pid 20235 appears to have left an orphan * process running in the background.* ERROR: sys-devel/gcc-4.9.3::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.9.3::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.9.3::gentoo'`.I am extremely hesitant to remove either of these packages from my system since both are necessary to compile. into the dependency graph, resulting in a slot conflict: sys-libs/glibc:2.2 (sys-libs/glibc-2.17:2.2/2.2::gentoo, ebuild scheduled for merge) pulled in by =sys-libs/glibc-2.17 (Argument) (sys-libs/glibc-2.9_p20081201-r2:2.2/2.2::gentoo, installed) pulled in by (no parents that aren't satisfied by other packages in this slot) It may be possible to solve this problem by using to prevent one of those packages from being selected.However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously.
* * Please include /var/tmp/portage/sys-devel/gcc-4.9.3/work/bz2 in your bug report.
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.9.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.9.3/temp/environment'.
The other vulnerabilities can possibly be exploited to cause a Denial of Service or leak information.
A number of mitigating factors for CVE-2015-7547 have been identified.
Please review the upstream advisory and references below.