Today's bit of libtool fun is that it uses "sed" to do some
macro-expansion - and the input line to "sed", when building Ethereal,
includes all the ".o" files for Ethereal.
Unfortunately, many "sed"s have a limit on the maximum size of an output
line - and I just hit the limit on Solaris 8's "/usr/bin/sed", with the
new dissectors.
A Google search for
+"Output line too long" +libtool
reveals that this problem occurs with other packages, and also reveals a
discussion on the libtool mailing list about this problem.
I don't know whether libtool 1.5 will work around that problem, or just
say "get GNU 'sed'". 1.4[.x] has its own problems, as we discovered a
while ago (a bunch of references to variables weren't quoted, so you got
syntax errors in "if test $xxx <op> <value>" statements in the shell
if the variables weren't set or were set to empty strings - and they do
happen not to be set or to be set to empty strings, at least on some
platforms).
"/usr/xpg4/bin/sed", as suggested on the libtool mailing list thread,
seems to work better, but there may well be other platforms on which
there's no native "sed" that does the job - and it'd be a pain to
require users building from source to tweak their path.
