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