bug#11060: libtool to_tool_file_cmd left undeclared and uninitialized

[Peter Rosin]

Peter O'Gorman skrev 2012-03-22 16:41:
> Hi David,
> 
> On 03/21/2012 06:32 PM, David C. Rankin wrote:
>> 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)
> 
> 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

That's not correct, above the outer case, there's
[#assume ordinary cross tools, or native build.
lt_cv_to_tool_file_cmd=func_convert_file_noop

My guess is a version mismatch between libtool.m4 and ltmain.{m4}sh,
or something such.

Cheers,
Peter