| 1 |
On Thu, 2003-12-04 at 19:54, Spider wrote: |
| 2 |
> begin quote |
| 3 |
> On Thu, 4 Dec 2003 20:36:12 -0500 |
| 4 |
> Mike Frysinger <vapier@g.o> wrote: |
| 5 |
> |
| 6 |
> > -----BEGIN PGP SIGNED MESSAGE----- |
| 7 |
> > Hash: SHA1 |
| 8 |
> > |
| 9 |
> > On Thursday 04 December 2003 20:26, Steven Elling wrote: |
| 10 |
> > > P.S. Developers: You might want to look into adding a number to the |
| 11 |
> > > '-j' |
| 12 |
> > > option in MAKEOPTS during emerges of certain packages to account for |
| 13 |
> > > this situation. |
| 14 |
> > |
| 15 |
> > i doubt that'll happen |
| 16 |
> > after all, some machines have 64 cpu's in them ... i think they might |
| 17 |
> > be able to handle the make fork bombing of glibc |
| 18 |
> |
| 19 |
> |
| 20 |
> quite true, and its just extra overhead to protect somone who should |
| 21 |
> know better. And, if you have more RAM it will work ;) (slowly, but |
| 22 |
> work) |
| 23 |
> |
| 24 |
> //Spider |
| 25 |
|
| 26 |
I did not mention it but I was using ccache and distcc with 3 machines |
| 27 |
(problem box included). |
| 28 |
|
| 29 |
I used to have 512MB of memory in this system but I had to rob 256MB for |
| 30 |
my server because one stick fried in it. I would buy more memory but my |
| 31 |
current job situation will not allow it. |
| 32 |
|
| 33 |
Oh, and I know better. It's just one of those problems I don't deal |
| 34 |
with that often and, when things go awry, I don't recognize it off the |
| 35 |
bat. However, I do know what to look at when problems occur. |
| 36 |
|
| 37 |
The only reason it took me a while to figure out what was going wrong is |
| 38 |
I didn't really care to look into the problem and left it for later. |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-dev@g.o mailing list |
Archives