On Thu, Jan 05, 2006 at 08:17:01PM -0800, Ken Robbins wrote > I just updated to gcc4.0.2 went ok did emerge -e system went good > then updated portage > now I trying to do emerge -e world it start off ok till it get to > ncurses start off in that ok, but then stop go back to the prompt no > error no noting to tell me what going on, before this I remove some > blockage faad2 xpdf > anyone know what up on this?
You're going to have a hard time believing this. I ran into this same problem some time ago on an older machine. The solution is to set MAKEOPTS="-j1" in /etc/make.conf and restart the emerge. There are one or two other packages for which this is necessary. I simply leave "-j1" on all the time. It's not worth the hassle when a compile blows up occasionally, and then switch MAKEOPTS back and forth. Yes, emerges are a bit slower, but consider how much time you "save" versus how much this one incident has cost you. Besides, you can usually emerge while working, or fire it up before going to bed. -- Walter Dnes <[EMAIL PROTECTED]> In linux /sbin/init is Job #1 My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
