Re: Error Building glibc 2.3.2
On Fri, 17 Oct 2003, Post, Mark K wrote:
Date: Fri, 17 Oct 2003 16:53:57 -0400
From: Post, Mark K [EMAIL PROTECTED]
Reply-To: Linux on 390 Port [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Error Building glibc 2.3.2
I figured it out. The process was using 115MB+ of virtual storage, and I
ran out of swap space. (The top command does have its uses.) Adding
another swap file allowed the command to finish. I have to say that Error
143 is _very_ uninformative in a case like this. :(
The way Linux handles out of memory errors sucks bunnies through
garden hoses (as jdow would say).
Remember to take a look at /var/log/{messages,syslog}, or run this:
dmesg | tail
from time to time when these things happen.
Most recently I found rsync consuming too much memory when backing up
20 Gbytes of data.
It ran out on both machines (target, source).
--
Cheers
John.
Join the Linux Support by Small Businesses list at
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Copyright John Summerfield. Reproduction prohibited.
Re: Error Building glibc 2.3.2
The only problem I've had with the build was with ustat.c (I assume it was to do with struct ustat mismatch). I'm currently running the test suite. -Original Message- I'm trying to compile glibc 2.3.2, using gcc 3.3. I ran into one problem with sysdeps/unix/sysv/linux/ustat.c that Gerhard Tonn helped me get around. Now, after it's done compiling (nearly) everything, the process is trying to build libc_pic.a, and getting this error:
Re: Error Building glibc 2.3.2
I figured it out. The process was using 115MB+ of virtual storage, and I ran out of swap space. (The top command does have its uses.) Adding another swap file allowed the command to finish. I have to say that Error 143 is _very_ uninformative in a case like this. :( Mark Post -Original Message- From: Ferguson, Neale [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 3:05 PM To: [EMAIL PROTECTED] Subject: Re: Error Building glibc 2.3.2 The only problem I've had with the build was with ustat.c (I assume it was to do with struct ustat mismatch). I'm currently running the test suite. -Original Message- I'm trying to compile glibc 2.3.2, using gcc 3.3. I ran into one problem with sysdeps/unix/sysv/linux/ustat.c that Gerhard Tonn helped me get around. Now, after it's done compiling (nearly) everything, the process is trying to build libc_pic.a, and getting this error:
Re: Error Building glibc 2.3.2
Mark Post wrote: I figured it out. The process was using 115MB+ of virtual storage, and I ran out of swap space. (The top command does have its uses.) Adding another swap file allowed the command to finish. I have to say that Error 143 is _very_ uninformative in a case like this. :( Well, 'make' says 'Error N' when the process it has started to build a target terminates with non-zero exit code N. Now, convention is that user processes normally use exit codes 128 to signal various sorts of abnormal exit conditions of their own; the kernel will set the exit code to 128 + signal number if it kills a process with a signal. This means your 'ld' process was terminated by signal 15 (SIGTERM). The only way this can happen (unless the signal was sent manually, e.g. using 'kill') is if the kernel's out-of-memory killer selected this task to kill in order to get out of a fatal out-of-memory situation. However, usually you'd get a SIGKILL (signal 9) from the OOM killer; this would have been displayed in a more obvious way by make (something like 'Killed'). I guess you're getting only a SIGTERM because you were running the build process as root? In any case, your /var/log/messages file will contain a line Out of Memory: Killed process ... Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
