libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../x86_64-kfreebsd-gnu/crti.o 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/crtbeginS.o  [*very long list of objects*] 
-Wl,--whole-archive ./.libs/libWebCore.a ./.libs/libWebCoreGtk.a 
-Wl,--no-whole-archive  -Wl,-rpath -Wl,/?PKGBUILDDIR?/build-2.0/.libs -lpthread 
./.libs/libjavascriptcoregtk-1.0.so /usr/lib/x86_64-kfreebsd-gnu/libenchant.so 
-lgailutil -lgeoclue -ldbus-glib-1 -ldbus-1 -lgstapp-0.10 -lgstaudio-0.10 
-lgstfft-0.10 -lgstinterfaces-0.10 -lgstpbutils-0.10 -lgstvideo-0.10 
/usr/lib/x86_64-kfreebsd-gnu/libgstbase-0.10.so 
/usr/lib/x86_64-kfreebsd-gnu/libgstreamer-0.10.so -lgmodule-2.0 -lgthread-2.0 
-lrt -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 
/usr/lib/x86_64-kfreebsd-gnu/libcairo.so -ljpeg -lsoup-2.4 -lgio-2.0 -lxslt 
-lxml2 -lGL -ldl -lpangoft2-1.0 -lpango-1.0 
/usr/lib/x86_64-kfreebsd-gnu/libfreetype.so -lfontconfig -lgobject-2.0 
-lglib-2.0 -lpng12 /usr/
lib/x86_64-kfreebsd-gnu/libsqlite3.so -licui18n -licuuc -licudata -lXrender 
-lXt -lX11 -lz -L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7 
-L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../x86_64-kfreebsd-gnu 
-L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../../lib 
-L/lib/x86_64-kfreebsd-gnu -L/lib/../lib -L/usr/lib/x86_64-kfreebsd-gnu 
-L/usr/lib/../lib -L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../.. -lstdc++ -lm 
-lc -lgcc_s /usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/crtendS.o 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../x86_64-kfreebsd-gnu/crtn.o  -O2 
-Wl,--as-needed -O2 -Wl,--version-script -Wl,../Source/autotools/symbols.filter 
-Wl,-z -Wl,relro -Wl,--export-dynamic -pthread -pthread   -pthread -Wl,-soname 
-Wl,libwebkitgtk-1.0.so.0 -o .libs/libwebkitgtk-1.0.so.0.13.2
collect2: error: ld terminated with signal 9 [Killed]

At first I thought it would be running out of memory. Note that we build
with -Wl,--no-keep-memory on 32 bit arches and so not here. But given that
a retry failed similarly I started a build on falla.d.o which failed
similarly. I then built with -Wl,--no-keep-memory only and with
-Wl,--no-keep-memory -Wl,--reduce-memory-overheads afterwards and it failed
both times. The failure is similar to the above.


I tried on my PC

It failed with 2GB RAM + 1.5 GB swap
with

  -Wl,--reduce-memory-overheads -Wl,--no-keep-memory

It passed linking of .libs/libwebkitgtk-1.0.so.0.13.2
with 2GB RAM + 4.5 GB swap with

  -Wl,--reduce-memory-overheads -Wl,--no-keep-memory, -Wl,--hash-size=31

The peak usage seen in top have been about 3 GB in ld.bfd.

Please, could it be rescheduled on buildd with really
lot of RAM and swap space ?

Petr


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to