|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
crosstool 0.43 ends with a sigkill?I'm building a toolchain for arm-xscale precessor with the configuration at the and of the post.
Crosstool correctly downloads all prerequisites but ends unexpectedly with the message "ld terminated with sigal 9 [sigkill]" Any ideas? It happens only (until now) with these configuration. I've tried others as the ones suggested in demo-arm-xscale.sh and all works good (unfortunatly I'm binded to these gcc-glibc-kernel combination) --------------------------------- This is my configuration: AR= BINUTILS_DIR=binutils-2.15 BINUTILS_EXTRA_CONFIG= BUILD=i686-pc-linux-gnu BUILD_DIR=/home/user/crosstool-0.43/build/arm-xscale-linux-gnu/gcc-4.0.0-glibc-2.3.6 CC= DEJAGNU= EXTRA_TARGET_CFLAGS= GCC_BUILD= GCC_CORE_DIR=gcc-4.0.0 GCC_DIR=gcc-4.0.0 GCC_EXTRA_CONFIG=--with-cpu=xscale --enable-cxx-flags=-mcpu=xscale GCC_HOST= GCC_LANGUAGES=c,c++,java GDB_DIR= GLIBC_ADDON_OPTIONS==linuxthreads, GLIBC_DIR=glibc-2.3.6 GLIBC_EXTRA_CC_ARGS= GLIBC_EXTRA_CONFIG= GLIBC_EXTRA_ENV= JUST_DOWNLOAD= KERNELCONFIG=/home/user/crosstool-0.43/arm.config LINUX_DIR=linux-2.6.21 LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0 NO_DOWNLOAD= PREFIX=/opt/crosstool/gcc-4.0.0-glibc-2.3.6/arm-xscale-linux-gnu PTXDIST_DIR= SHARED_MODE=--enable-shared SRC_DIR=/home/user/crosstool-0.43/build/arm-xscale-linux-gnu/gcc-4.0.0-glibc-2.3.6 TARBALLS_DIR=/home/user/downloads TARGET=arm-xscale-linux-gnu TARGET_CFLAGS=-O TOP_DIR=/home/user/crosstool-0.43 USE_SYSROOT= |
|
|
Re: crosstool 0.43 ends with a sigkill?Probably a clue:
I realized that if I try to build with option GCC_LANGUAGES="c,c++" rather than GCC_LANGUAGES="c,c++,java" the crosstool is built correctly.
|
|
|
Re: crosstool 0.43 ends with a sigkill?2007/11/15, Omone <alessandro.castrucci@...>:
> Crosstool correctly downloads all prerequisites but ends unexpectedly with > the message > "ld terminated with sigal 9 [sigkill]" > Any ideas? That's what normally happens when your machine runs out of virtual memory: the kernel kills whatever process requested "more memory" than it has. Signal 9 is also characteristic of this. You can verify this by running "vmstat 5" on a separate console: if the "free" and "cache" columns go down to 4 digits just before it happens, this is your problem. If you have swap enabled on your build host, you may also see the "swapped" column rise to a maximum, and the "si so" columns go frantic; there will also be a lot of disk-read activity as the kernel in it last efforts to keep the show going deallocates pages of program text only to find that it needs to fetch them back in again from disk. The last lines of the output of "dmesg", if you run it just after the crash, should also be illuminating. Other than adding more RAM, you could try configuring some (or some more) swap space on your build host - get back in touch if you need pointers on how to do this. M -- For unsubscribe information see http://sourceware.org/lists.html#faq |
|
|
Re: crosstool 0.43 ends with a sigkill?Thank you very much Martin,
luckily I'm running crosstool under a VMWare, so I was able to set more RAM for the host machine and all worked good!
|
| Free embeddable forum powered by Nabble | Forum Help |