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