Jack wrote: > Not far enough back. You need to show the actual error, not the line > "Error1:" which gets printed after the error. >
And depending on the number of cores/threads and other emerge settings, it can be a dozen, two dozen lines or sometimes even further back than that. With CPUs having a dozen or so cores/threads, it's amazing that some stuff compiles at all. Prime example, recent thread about Pam updates. OP, if needed, tar the whole error log and attach it. Just don't post it elsewhere and link to it tho. After a while, it's gone or a person finds the log but not this thread with the solution. Dale :-) :-)
