bug#11060: libtool to_tool_file_cmd left undeclared and uninitialized

[David C. Rankin]

Guys,

  I have a libtool problem that occurs in the trinity build of tdeutils
(kdeutils) which includes libtool (2.2.6b Debian-2.2.6b-2ubuntu1). I have
libtool 2.4.2 installed on my system. The 'libtool' executable created by
./configure fails to declare or initialize 'to_tool_file_cmd'. This results in a
build failure for every file when make is run. (the call in the libtool file 
is):

$to_tool_file_cmd $1  (or "" $1 when uninitialized)

  I have included a link to the trinity desktop bug report below that provides
more details. What I need to know is "What's the best way to fix this?" I have a
work-around that explicitly sets to_tool_file_cmd to its default
‘func_convert_file_noop’ (post-configure using sed), but I need to know is this
a bug in libtool that allows the variable to remain uninitialized?"

  Running 'libtool --force' or 'autoreconfig --force' does not correct the
issue. I would appreciate any thoughts you would have.

Trinity bug report with additional details is here:

http://bugs.pearsoncomputing.net/bugzilla/show_bug.cgi?id=924

  The basic build script that leads to this failure is the following:

  cd ${srcdir}/${pkgname#*-}
  cp /usr/share/aclocal/libtool.m4 ./admin
  cp /usr/share/libtool/config/ltmain.sh ./admin

  make -f admin/Makefile.common

  ./configure \
    --prefix=${TDEDIR} \
    --with-qt-dir=${QTDIR} \
    --sysconfdir=/etc \
    --localstatedir=/var \
    --enable-debug=full \
    --enable-closure

  make

  In order for libtool to work, I have to include the following after
./configure to fix the libtool executable created:

sed -i '/#! \/bin\/sh/s|$|\n\nto_tool_file_cmd=func_convert_file_noop\n|' 
libtool

  What say the experts?

-- 
David C. Rankin, J.D.,P.E.