Today's emerge of the glibc update from 2.18-r1 to 2.19 failed to complete the compile phase (near the end). I'm on a profile of x86-64bit, current, desktop, hardened. All packages were up to date as of yesterday. I have two questions: (1) should I perhaps update binutils manually first with the old glibc and then try building a clean toolchain with the new glibc? (2) should I abandon the hardened profile, if that is part of the problem, and if so how to switch "hardened" off?
Notice the message "Cannot allocate memory" -- there is 16 Gbytes of ram here and plenty of free mem during this compile. My best wild guess is that my hardened binutils/gcc are throwing the error.
I have had Funtoo pure64 - current - desktop - NOT hardened - running on another partition. Glibc and friends updated just fine there of course. If no one has other advice for me I'll switch back to that installation, add zfs to it and get it working with my zfs raidz pool.
Am (Was) I the only one running a hardened profile on Funtoo?? This is my second show-stopper with "hardened": I couldn't run zfs on a hardened kernel and had to switch to gentoo-sources, and now can't emerge glibc-2.19 on a hardened toolchain.
Question
sitquietly
Today's emerge of the glibc update from 2.18-r1 to 2.19 failed to complete the compile phase (near the end). I'm on a profile of x86-64bit, current, desktop, hardened. All packages were up to date as of yesterday. I have two questions: (1) should I perhaps update binutils manually first with the old glibc and then try building a clean toolchain with the new glibc? (2) should I abandon the hardened profile, if that is part of the problem, and if so how to switch "hardened" off?
The glibc error is here:
Notice the message "Cannot allocate memory" -- there is 16 Gbytes of ram here and plenty of free mem during this compile. My best wild guess is that my hardened binutils/gcc are throwing the error.
Here's emerge --info glibc:
Advice?
[EDIT]
I have had Funtoo pure64 - current - desktop - NOT hardened - running on another partition. Glibc and friends updated just fine there of course. If no one has other advice for me I'll switch back to that installation, add zfs to it and get it working with my zfs raidz pool.
Am (Was) I the only one running a hardened profile on Funtoo?? This is my second show-stopper with "hardened": I couldn't run zfs on a hardened kernel and had to switch to gentoo-sources, and now can't emerge glibc-2.19 on a hardened toolchain.
Link to comment
Share on other sites
6 answers to this question
Recommended Posts