The ebuild in summary is currently forcing users to use serial make (-j1, no extra job tasks). This seems not to be needed. The ebuild was modified to use -j8 on a truly 8-core SMP system and didn't fail the build, you should either check if it's a particular USE flag to cause the problem, or drop -j1 and leave the user to decide how many jobs to use. I want to remember you that with modern multicore systems, forcing serial make is going to waste a lot of time and resources for users.. Thanks, Diego
a) I won't touch xerces-c-2.7.0 anymore since it'll be obsolete once I stable 2.8.0 b) I've tested xerces-c-2.8.0 with -j5 on a truly 4-core SMP systen and it did fail. You know that parallel make jobs may exhibit random build failures depending on various factors (available RAM, number of jobs running at the same time, etc.) You might also take a look at bug #101657 which states that 2.6.0 already has a problem with -jN, N>1 and notice that the build system didn't change since then. So, either _you_ are going to check the build system whether it now works and fix it if it doesn't or stop reporting such bugs since we have a lot of other stuff to do. Thanks.
I'm closing this now since the build system got reworked for 3.0.0 and we don't set -j1 there anymore
