Hello,

In GNOME project, we have severl machines running as tinderboxes,
continuously building all our modules from CVS.  In a lot of logs
from these builds I'm seeing these lines:

/usr/bin/libtoolize: line 93: echo: write error: Broken pipe
/usr/bin/libtoolize: line 94: echo: write error: Broken pipe

which I believe is caused by the echo commands in libtoolize's
--version feature when run as "libtoolize --version | head 1"
(from gnome-autogen.sh) under some probably heavy loads on the
system, making the head command terminate before libtoolize or
something like that...

As I'm not seeing similar errors from other tools we run the same
way, I'm wondering whether libtoolize can be made to ignore
SIGPIPE, at least in --version...

Thanks,

--behdad


_______________________________________________
Bug-libtool mailing list
Bug-libtool@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool

Reply via email to