On 03/23/2012 10:54 AM, David C. Rankin wrote:
> On 03/22/2012 07:43 PM, David C. Rankin wrote:
>> Confirmed,
>>
>> Libtool version mismatch resulting in undeclared 'to_tool_file_cmd' is common
>> to all tde modules requiring autoconf. With tdeaddons, after issuing:
>
> I have filed a bug report with gnu regarding the libtool issue and I'm
> currently working with the developer. So far, here is the initial response I
> have received:
>
>  > It looks like this isn't getting set to the default in libtool.m4, but it's
>  > strange that our test suite didn't notice (and that this is the first report
>  > of it).
>  >
>  > Could you please send me a failing build log, and perhaps run a failing
>  > libtool command with an added --debug flag (right after the 'libtool') and
>  > send the output of that also.
>  >
>  > Then we can come up with a test that fails, right now it seems the fix is
>  > something like:
>  >
>  > diff --git a/m4/libtool.m4 b/m4/libtool.m4
>  > index 75bfdb4..45a988f 100644
>  > --- a/m4/libtool.m4
>  > +++ b/m4/libtool.m4
>  > @@ -7862,6 +7862,9 @@ case $host in
>  > ;;
>  > esac
>  > ;;
>  > + * ) # unhandled hosts (and "normal" native builds)
>  > + lt_cv_to_tool_file_cmd=func_convert_file_noop
>  > + ;;
>  > esac
>  > ])
>  > to_tool_file_cmd=$lt_cv_to_tool_file_cmd
>  >
>  >
>  > Thanks,
>  > Peter
>
> I'll keep you posted as I get more information.
>

Well, it isn't a libtool bug, but problem with the current setup on the TDE 
code. Here is the response from the gnu:

<quote>

close 11060
tags 11060 notabug
thanks

Hi David,

On 03/23/2012 10:44 AM, David C. Rankin wrote:
 > On 03/22/2012 10:41 AM, Peter O'Gorman wrote:
 >
 > Peter,
 >
 > Attached is the config.log, the failing libtool and the tdeutils
 > build.log. I apologize that I couldn't immediately figure out where to
 > put the '--debug' to make it appear right after libtool? (Makefile?,
 > CFLAGS?) If I haven't given you what you need, just let me know and I'll
 > send it. The error is clear:

I think there is another copy of a different version libtool.m4 inculded in 
acinclude.m4, and that's causing the problem

The libtool m4 macros that match the ltmain script do properly set these 
variables as Peter noted yesterday.

To update the included libtool, you will have to edit acinclude.m4 also.

Thanks,
Peter

</quote>

I know nothing about the autoconf syntax or wizardry that goes on inside the 
files, so we will need to find someone on the list that has that knowledge to 
help with the code fix.  I'll update the bug report with this information.


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