On Tue, Jul 15, 2014 at 12:33:57AM -0500, Dale wrote: <SNIP> > > make -j3 -s glibc-test > > * Your old kernel is broken. You need to update it to > > * a newer version as syscall(<bignum>) will break. > > * http://bugs.gentoo.org/279260 > > * ERROR: sys-libs/glibc-2.17::gentoo failed (setup phase): > > * keeping your system alive, say thank you > > * > > * Call stack: <SNIP> > UPDATE: Thanks to Hinnerk, the locale error is fixed. I am still > looking for ideas on the glibc error tho. Since this original post, I > have tried the following versions of glibc with the same result. > > sys-libs/glibc-2.18-r1 > sys-libs/glibc-2.19-r1 > > So, it seems something else is wrong here. I have googled and most > things I find are with older kernels and I'm using the newest kernel I > can find in the tree. 3.15.5-gentoo > > Ideas? Fixes? Bug that needs Raid?
I've taken a look at the bug that is mentioned in the error and there were
several things mentioned that are supposed to fix this:
1. disable auditd (if you have it running) - this was the newest (from
'14)
So if you have it installed run /etc/init.d/auditd stop
2. reemerge several packages because python may have issues:
- sync your tree
- emerge portage (which will likely pull in some python stuff if the
box
wasn't updated for some time)
(- optional: run eselect python and select a sane version and run
python
updater - this wasn't mentioned but may make sense nonetheless)
- emerge linux-headers
- emerge glibc (hopefully with success this time)
WKR
Hinnerk
signature.asc
Description: Digital signature
