On Wednesday 08 March 2006 13:02, Duncan wrote: > I'm running a dual Opteron (242) here, and routinely run MAKEOPTS="-j6 > -l6" here, plus sometimes run multiple parallel emerges (using emerge -tp > first to see what the dependencies are, then emerge -a to verify that the > same dependency isn't in both). > > As I'm running ~amd64, plus running way out front with still-masked gccs > (now gcc-4.0.2-rX and gcc-4.1.0), which sometime last year (with > gcc-4.0.0) required still experimental glibcs if I wanted to compile themm > with the new gcc, I tend to do more merging of everything, including > glibc, than most, and IDR ever having that sort of issue. > > Occasionally, there's an ebuild that has parallel job issues, but they > tend to be pretty rare, because as they are found and bugged, the ebuild > will be adjusted to filter out the -jX and force serial compilation jobs. > In fact, a quick: "grep MAKEOPTS /p/sys-libs/glibc/*|grep j1" returns a > huge number of hits, multiple per ebuild, where serial compilation is > already forced by the various glibc ebuilds. > > Assuming you didn't manually filter all those forced -j1 calls, all I can > say is perhaps another one or more need added. They apparently haven't > been triggered for most of us or it'd already be forced, but maybe your > machine just happens to trigger it in a different area. <shrug> Either > that or there's something strange going on with your bash or make or the > like and it's filtering the wrong thing. > > What glibc are you attempting to merge, what are your bash, portage, gcc, > and make versions, and where exactly is the error? If you know bash > scripting well enough to follow what the ebuild is doing, it shouldn't be > hard to verify whether the problem make calls are forcing -j1 or not (some > in the glibc ebuilds do, some don't).
Thank you for this detailed reply. I always like to read your really very informative contributions to the gentoo mailing lists. As to your questions I cannot tell what the versions of bash portage etc. were. I emerged glibc during my migration from the 2004.3 profile to the 2005.0 profile which is now complete. During the migration new versions of bash, portage and so an were merged. Now all is new and works! I cannot reproduce the loop. What happened was, that the emerge of glibc started to loop at a certain point. I then killed the emerge, issued the same command again and the merge started to loop at another point. I'll let MAKEOPTS set and observe what happens in future. Thanks to all who answered. -- ________________________________________________________________ Hans-Gunther Borrmann <[EMAIL PROTECTED]> Rechenzentrum der Universitaet Freiburg Hermann-Herder-Str. 10, D79104 FREIBURG Tel.: +49 761/203-4652 Fax: +49 761/203-4643 -- [email protected] mailing list
