| 1 |
On Wednesday 22 Feb 2012 07:11:15 Mick wrote: |
| 2 |
> On Wednesday 22 Feb 2012 00:22:27 Philip Webb wrote: |
| 3 |
> > 120222 Nikos Chantziaras wrote: |
| 4 |
> > > On 22/02/12 00:34, Alex Schuster wrote: |
| 5 |
> > >> Mick writes: |
| 6 |
> > >>> The latest stable x86 firefox fails to compile: |
| 7 |
> > >> [... big linking being done ...] |
| 8 |
> > >> |
| 9 |
> > >>> collect2: ld terminated with signal 9 [Killed] |
| 10 |
> > >>> make[5]: *** [libxul.so] Error 1 |
| 11 |
> > >> |
| 12 |
> > >> [...] |
| 13 |
> > >> Do you have enough memory on that machine, is swap space activated? |
| 14 |
> > >> The linking phase will need a lot of memory. |
| 15 |
> > >> Although I don't understand why ld would terminate with signal 9 then. |
| 16 |
> > > |
| 17 |
> > > When there's not enough memory available, signal 9 is actually |
| 18 |
> > > how the system recovers from that, by killing the offending process. |
| 19 |
> > > dmesg should have given a clue about what happened in that case. |
| 20 |
> > |
| 21 |
> > I compiled FF 10.0.1 on amd64 without any problems : |
| 22 |
> > it needed 3,61 GB disk space for the link stage |
| 23 |
> > & most/all of my 2 GB memory. |
| 24 |
> |
| 25 |
> Thanks guys, I did add half a gig of swap just in case to the 250M already |
| 26 |
> available. It may be that this old box is now soooo old that I can no |
| 27 |
> longer emerge FF on it. I will try adding some more swap (which of course |
| 28 |
> will take away available disk space for /var/portage) and see what I run |
| 29 |
> out of. |
| 30 |
> |
| 31 |
> PS. I was expecting some message on screen saying "no space left on |
| 32 |
> device", but have not checked dmesg for running out memory errors. |
| 33 |
|
| 34 |
I increased the swap to 1G and emerged without memory errors this time. I'll |
| 35 |
remember to check dmesg first next time I emerge a big package. |
| 36 |
-- |
| 37 |
Regards, |
| 38 |
Mick |
Archives