| 1 |
On Mon, 2009-07-06 at 17:53 -0400, Mike Edenfield wrote: |
| 2 |
> On 7/6/2009 4:23 PM, Jarry wrote: |
| 3 |
> > Mike Edenfield wrote: |
| 4 |
> >> On 7/6/2009 2:23 PM, Jarry wrote: |
| 5 |
> |
| 6 |
> >>> MAKEOPTS="-j2" |
| 7 |
> |
| 8 |
> >> Can you try this again without -j2 in the make opts? The gcc build |
| 9 |
> >> process is enough of a pain to debug when you can see output |
| 10 |
> >> sequentially, running parallel makes makes it worse. |
| 11 |
> |
| 12 |
> > Now this is strange: I commented out that MAKEOPTS="-j2" in make.conf |
| 13 |
> > and gcc compilled without any complaint. I did not change anything |
| 14 |
> > else! Can't believe this. I will check it tomorrow again, with -j2 |
| 15 |
> > and without... |
| 16 |
> |
| 17 |
> I can't explain why this happens but I do know that I've seen a number |
| 18 |
> of complex builds (especially gcc/glibc) that just randomly fail when |
| 19 |
> using a parallel make. I see this effect on FreeBSD moreso than Gentoo, |
| 20 |
> but I suspect that's only a question of scale. |
| 21 |
> |
| 22 |
> --Mike |
| 23 |
> |
| 24 |
|
| 25 |
Try MAKEOPTS="-j1" - the default is still j2 if you just delete the |
| 26 |
variable. |
| 27 |
|
| 28 |
Ive also seen this a lot recently. Serialising the make process into |
| 29 |
one thread helps. |
| 30 |
|
| 31 |
BillK |
Archives