On Thursday 04 January 2007 23:37, Dale wrote: > Peter Alfredsen wrote: > > On Thursday 04 January 2007 19:39, Dale wrote: > >> Anybody know how to fix this? > > > > Yeah, -r4 fails for me too. -r5 compiles beautifully, though. > > Just add this line to /etc/portage/package.keywords: > > =sys-apps/util-linux-2.12r-r5 ~x86 > > > > And re-emerge it. > > > > HTH > > Oh, may try that. I'm using a script that I found on the forums to do > this instead of emerge -ev world. It is something I found when updating > gcc a good while back. According to some emerge doesn't do them in the > correct order but this script does. It starts out with the kernel so it > is different.
Yes, I've read about that. Looks nice. There should be file where you can alter stuff like this, IIRC. > Now to go figure out how to get this script to emerge that version > without starting over. ;) > > Now to figure out what the deal was on my CFLAGS. I think your CFLAGS are probably fine. I have sane (march, pipe, fomitframepointer) CFLAGS and the problem is still there. If they've worked for you before with no problems, they will probably work for you again. I think your problem probably is that you're trying to build a system based off a 2.6.19 kernel/headers while remaining in stable for the rest of the tree. I guess that this is the case because there is only one significant difference between -r4 and -r5 of util-linux: > 31 Oct 2006; Mike Frysinger <[EMAIL PROTECTED]> > +files/util-linux-2.12r-no-_syscall.patch, util-linux-2.12r-r5.ebuild: > Fix building with linux-headers-2.6.18+ as _syscall#() no longer exists > #150852 by Mario Fetka. This will not work without a lot of unmasking. Only ~x86 is fully patched for 2.6.19. -- /PA -- gentoo-user@gentoo.org mailing list
