make[2]: Entering directory
`/var/tmp/portage/app-benchmarks/siege-2.61-r1/work/siege-2.61/lib/joedog'
/bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I. -I../../include -W -Wall -O2 -pipe -march=pentium-m -fomit-frame-pointer
-c -o error.lo `test -f error.c || echo './'`error.c
../../libtool: line 323: s,^.*/,,g: No such file or directory
../../libtool: line 737: -e: command not found
*** Warning: inferring the mode of operation is deprecated.
*** Future versions of Libtool will require --mode=MODE be specified.
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1048: -e: command not found
../../libtool: line 1100: -e: command not found
: compile: cannot determine name of library object from `'
make[2]: *** [error.lo] Error 1
This looks libtool-related. I have 1.5.24 on this system which is the latest
stable version atm.
siege-2.66, the latest unstable version, compiles fine, so fixing this could
simply be a matter of asking for a newer version to be stabilized.
(In reply to comment #0)
> siege-2.66, the latest unstable version, compiles fine, so fixing this could
> simply be a matter of asking for a newer version to be stabilized.
Sounds like a plan... :)