This problem I also have (on amd64). libtool generates many 'sh' sessions, that brings down the system. This happens when building within kdevelop, but also by hand. I get messages like
/bin/sh ../libtool --tag=CXX --mode=link g++ -g -O2 -mwindows -o tau agent.o brain.o brainmodule.o distributions.o field.o global.o land.o main.o object.o objectdraw.o owner.o userinterface.o ziggurat.o ../libtool: fork: Resource temporarily unavailable ../libtool: fork: Resource temporarily unavailable ../libtool: fork: Resource temporarily unavailable ../libtool: fork: Resource temporarily unavailable ../libtool: fork: Resource temporarily unavailable ../libtool: line 718: *** Warning: inferring the mode of operation is deprecated.: command not found ../libtool: line 719: *** Future versions of Libtool will require -mode=MODE be specified.: command not found ../libtool: line 718: *** Warning: inferring the mode of operation is deprecated.: command not found ../libtool: line 719: *** Future versions of Libtool will require -mode=MODE be specified.: command not found ../libtool: line 751: : warning: cannot infer operation mode without MODE- ARGS: command not found ../libtool: line 6512: : you must specify a MODE: command not found ../libtool: line 751: : warning: cannot infer operation mode without MODE- ARGS: command not found ../libtool: line 6513: Try ` --help' for more information.: command not found ../libtool: line 6512: : you must specify a MODE: command not found ../libtool: line 6513: Try ` --help' for more information.: command not found etc. Mathijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
